Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.6k
[Config] Deprecate ArrayNodeDefinition::ignoreExtraKeys in favor of s etIgnoreExtraKeys and setRemoveExtraKeys#47284
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:7.4
Are you sure you want to change the base?
Conversation
770f209
to446ced9
Compare@carsonbot find me a reviewer please |
carsonbot commentedOct 29, 2022
I'm sorry. I could not find any suitable reviewer. |
…etIgnoreExtraKeys and setRemoveExtraKeys
446ced9
toff56741
CompareI rebased branch on 6.3, I'm looking for reviewers 😄 |
I like this proposal ... but the new method names look a bit odd compared to the rest of methods:
Maybe we could use these names instead:
This is a bit more complicated because we need to handle differently the deprecation of the current behavior of |
Uh oh!
There was an error while loading.Please reload this page.
ArrayNodeDefinition::ignoreExtraKeys($bool)
is ambiguous, it controlArrayNode::ignoreExtraKeys
andArrayNode::removeExtraKeys
at the same time.Introduce unambiguous methods and deprecate
ignoreExtraKeys
(It's seems better than create human helper constant)
(Unrelated fabbot failure)