Really deprecate comparing AC::Parameters with a hash#44812
Merged
tenderlove merged 1 commit intomainfrom Mar 31, 2022
Merged
Conversation
PR #23733 was supposed to deprecate and remove the ability to compare Hash objects with AC::Parameters objects. Unfortunately it seems that we still accidentally support that. This PR adds a deprecation warning so that we can remove it in the future.
rafaelfranca
approved these changes
Mar 31, 2022
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.
PR #23733 was supposed to deprecate and remove the ability to compare
Hash objects with AC::Parameters objects. Unfortunately it seems that
we still accidentally support that.
This PR adds a deprecation warning so that we can remove it in the
future.
Unfortunately the deprecation message is showing for a few tests and I'm not 100% sure how we should proceed.
We are delegating some methods to the underlying hash, but other methods have their own implementation.
One specific example is
ActionController::Parameters#valuesvsActionController::Parameters#each_value. These two methods can hand back different objects:Output is:
The above behavior leads to an odd case where
params.valuesdoesn't equalparams.each_value.to_aand we have a test for that here.IMO we need to stop delegating any methods to the underlying hash, or at least drastically restrict them, but I'm somewhat worried about compatibility.