You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 19, 2018. It is now read-only.
This seems less useful than to_key unless for and name params do some magic, which I think they probably shouldn't. As there's no obvious "right" way of naming for/name in HTML (there's probably multiple competing conventions like there are with BEM/OO CSS etc), so I guess many would override this anyway, so we could just leave them to add it in ApplicationRecord themselves.
If Hyerloop had its own form_builder replacement smart input components then this would be a part of it.
But a one size fits all form builder is hard. The Rails one isn't flexible enough to work with frameworks like Bootstrap, so then there was SimpleForm but that's nowhere near simple, I hate it. I'd suggest holding off on this issue until we have a more concrete use-case for it.
are the conventions used by any code? As in would I ever "have" to use the convention, or is it just simply a convention to keep things tidy. In which case it seems like it might be helpful. but I dunno. We can drop it from 1.0 if all agree...
See ruby-hyperloop/hyper-react#245 for how I use this in a smart form input component. Simply some human readable and useful yet unique identifier to link name and from
just a handy helper to add the ActiveRecordBase (on the client) (it would jus be added to InstanceMethods module)
See ruby-hyperloop/hyper-react#244 for details on
to_key
The text was updated successfully, but these errors were encountered: