AR update_attributes api is updated to reflect the addition of assign_att #311
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
martinploeger
pushed a commit
to martinploeger/rails
that referenced
this pull request
Apr 26, 2011
AR update_attributes api is updated to reflect the addition of assign_att
|
Merged, thanks! |
|
Or maybe not merged! I am confused! |
|
its merged, its in the commits list :) for some reason GH doesn't close pull requests automagically :( |
|
Ok. I'll close this. Thanks for verifying! |
arunagw
pushed a commit
to arunagw/rails
that referenced
this pull request
Apr 26, 2011
AR update_attributes api is updated to reflect the addition of assign_att
matthewd
pushed a commit
that referenced
this pull request
Apr 24, 2018
`Extract#as` should not mutate the receiver
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hey Guys,
This brings AR update_attributes in line with assign_attributes in accepting a scope using :as or bypass mass-assignment security using :without_protection => true
Thanks,
J