Nate Eizenga

Adding a problem to the mix: nested singular resources are currently broken and cannot benefit from a fix via `resolve`. To illustrate, consider ```ruby # config/routes.rb resources :users do resource...

> Thanks for your input. My PR doesn't use resources. I tested your use case and it works fine in my suggested fix linked in the above PR. Understood, but...

> That's why I asked if it would be correct to change the current convention and that resource ... internally sets the `resolve` I don't have the context to say...

> I don't currently have a fix but another current workaround is to specify the `format` in your form: > > ```ruby > > ``` Setting the url keyword argument...

Once again: resolve is _not a working solution for nested singular resources_. If it is intended to be our blessed-path solution, then this inadequacy should be addressed.

> I've decided to open this back up for the time being given that the nested resources will not work with resolve. I could open an issue specific to this...

> I'm hitting the same issue and for some reason the `ASDF_RUBY_BUILD_VERSION` in `~/.asdf/plugins/ruby/lib/utils.sh` is downgraded? I didn't do this manually: > > ~/.asdf/plugins/ruby/ruby-build (git)-[master] % git status > On...

Sounds good! Want me to add any of the other keys in that metadata? Happy to do the work, but don't want to put words in your mouth a-la "GitHub...

Hopefully my proof-of-concept provides enough clarity! I'd be happy to open a PR implementing the described behavior, but would prefer a 👍 with regard to the proposed handling of permitted_attributes...