Updates the form class names to use rails pattern #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The problem
When creating the form field with the Attachy helper, things worked fine for classes with single word names, like
User
, with the#downcase
method. But when the class had a composed name likeAdminUser
the result would beadminuser
since#downcase
only replaces uppercase chars with the downcased version.Before example:
The solution
Rails uses the
#underscore
method to generate the downcased underscore separed class names to generate form. So when composed words classes use the attachy helper the field would come in a different form data.After example