Closed JuanVqz closed 9 months ago
@JuanVqz I think I found the issue why these changes looked weird to me, the error this is solving is only present in next_rails < 1.1.0, but it was already fixed
before 1.1.0 the arguments are NOT optional and that's why it's complaining about, since 1.1.0 the arguments are optional and there's no issue
I think we should close this PR, no need to change anything
@arielj thanks for doing the research on it! sure, I'm closing it.
Closes https://github.com/fastruby/next_rails/issues/108