Activemode::Dirty attributes query methods consistency before and after saving.#19847
Merged
rafaelfranca merged 1 commit intoApr 21, 2015
Merged
Activemode::Dirty attributes query methods consistency before and after saving.#19847rafaelfranca merged 1 commit into
rafaelfranca merged 1 commit into
Conversation
`ActiveModel::Dirty#[attr_name]_previous_change` to improve access to recorded changes after the model has been saved. It makes the dirty-attributes query methods consistent before and after saving.
rafaelfranca
added a commit
that referenced
this pull request
Apr 21, 2015
…-syntactic-sugar Activemode::Dirty attributes query methods consistency before and after saving.
This file contains hidden or 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
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.
Provides
ActiveModel::Dirty#[attr_name]_previously_changed?andActiveModel::Dirty#[attr_name]_previous_changeto improve access to recorded changes after the model has been saved.It makes the dirty-attributes query methods consistent before and after saving. It comes handy when attribute changes are inspected in controllers, services objects and so on.