Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add slice! method to ActiveModel::Errors #34489

Merged
merged 1 commit into from Nov 21, 2018
Merged

Add slice! method to ActiveModel::Errors #34489

merged 1 commit into from Nov 21, 2018

Conversation

6temes
Copy link
Contributor

@6temes 6temes commented Nov 20, 2018

Summary

ActiveModel::Errors implements several methods from Hash but not all of them.

The method slice! is provided to Hash via ActiveSuport and it could be really convenient to have it as well in ActiveModel::Errors for situations when the developer needs to delete several errors from a model.

@rails-bot
Copy link

Thanks for the pull request, and welcome! The Rails team is excited to review your changes, and you should hear from @georgeclaghorn (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

This repository is being automatically checked for code quality issues using Code Climate. You can see results for this analysis in the PR status below. Newly introduced issues should be fixed before a Pull Request is considered ready to review.

Please see the contribution instructions for more information.

# person.errors.slice!(:age, :gender) # => { :age=>["cannot be nil"], :gender=>["cannot be nil"]}
# person.errors.keys(:name, :age) # => [:name]
def slice!(*keys)
keys.inject({}) do |acc, key|
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The messages and details are both hashes. I think it makes more sense for us to just use slice! on those like we do with merge!, right?

person.errors.add(:gender, "cannot be nil")
person.errors.add(:city, "cannot be nil")

removed_errors = person.errors.slice!(:age, :gender)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need a test with string keys, since all other methods support both strings and symbols.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure!

Should I mix strings and symbols in this test or is it better to create another test just for that?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can mix them if you want.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, I understand! This method should allow strings or symbols to be passed indifferently. I have a failing test now.

Copy link
Member

@rafaelfranca rafaelfranca left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good. Can you add a CHANGELOG entry and also squash all commits in one?

@6temes
Copy link
Contributor Author

6temes commented Nov 21, 2018

Done!

Tests are passing now.

@rafaelfranca rafaelfranca merged commit 3269506 into rails:master Nov 21, 2018
@rafaelfranca
Copy link
Member

Thank you so much! Nice work

@6temes 6temes deleted the add_slice_method_to_errors branch November 21, 2018 22:46
suketa added a commit to suketa/rails_sandbox that referenced this pull request Aug 3, 2019
Add slice! method to ActiveModel::Errors
rails/rails#34489
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants