Mass-assignment can work with a stringified hash #14
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.
Hello,
We came across an issue where mass assigning a stringified hash of attributes would raise a
KeyError
if any of those attributes were uninitialized on the object that mixes inShallowAttributes
.Example:
And this is the type of error you would get:
The reason we get this error is because of how we use ShallowAttributes with our form objects.
before_action
and then we update the form object with the POST data.ActionController::StrongParameters
) rather than a symbolized hash.This patch changes the behaviour to make mass assignment work with both stringified and symbolized hashes. Given
to_sym
on symbols is a no-op there should be minimal overhead to projects using symbolized hashes.Happy to have any feedback 😄
Cheers,
Tate