Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[OptionsResolver] Add $triggerDeprecation arg to offsetGet() method in Options interface#31799
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
Uh oh!
There was an error while loading.Please reload this page.
Conversation
yceruto commentedJun 2, 2019 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
We lack a deprecation notice in 4.4 :/ this is a special case. I think |
yceruto commentedJun 2, 2019 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Or at least trigger only if the number of arguments in the real method is less than the ones defined in |
dc55eea tob8cd9baCompareb8cd9ba tod983fd8Comparenicolas-grekas commentedJun 3, 2019
I agree |
nicolas-grekas commentedJun 3, 2019
(don't forget the UPGRADE files :) ) |
yceruto commentedJun 3, 2019
Yes, I think so :) |
nicolas-grekas commentedJun 3, 2019
Adding |
nicolas-grekas commentedJun 8, 2019
Actually I'm proposing to remove the argument from the interface in#31950 |
| * @throws NoSuchOptionException If the option is not set | ||
| * @throws InvalidOptionsException If the option doesn't fulfill the | ||
| * specified validation rules | ||
| * @throws OptionDefinitionException If there is a cyclic dependency between |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
all this is not a minor change: was it implicitly the definition of the contracts of the interface before?
also, does it make sense to have all this at the abstraction level? or are they implementation details of OptionsResolver, the implementation?
Ref:#28878