Wednesday, February 19, 2020
I'm not suggesting any breaking changes at all.
I've been using Rails since Rails version 2 so I don't know what you mean "like that from the beginning"
In the beginning, DHH said things would "just work" and, as a community we would value convention over configuration.
As far as using ActiveModel with the form_with, I don't think that's relevant, it wouldn't make any difference as to behavior.
All I'm suggesting is that Turbolinks is too complicated and should be OFF by default, like a lot of other things, so that it could be opted-into by the dev instead of forced upon us by the framework.
On Tuesday, February 18, 2020 at 1:41:03 PM UTC-5, San Ji wrote:
I don't think you can blame Rails 6 for that. It is a weird default, but it is like that from the very beginning.
I never use the method, so, I guess, it can be considered as somewhat obscure. It seems to appear in Rails version 5.1 and no change since.
Normally, I would use ActiveModel for a local form. Just in case you don't know, ActiveModel can also be used independently from ActiveRecord.
This is the earliest docs I found.
https://api.rubyonrails.org/v5.1/classes/ActionView/ Helpers/FormHelper.html# method-i-form_with
Guess someone already complained, but it is too late; there is no good reason to introduces breaking changes for a better default.
Also, in a sense, this can be the better default, since ActiveModel is there for you to build a form for the same app.
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/24f5f9ba-0d91-4279-bf10-841c06a2463a%40googlegroups.com.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment