-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[OptionsResolver] Changed order of validation #11501
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
Conversation
👍 |
@sstok is talking about "filtering". Not sure what he means. Filtering is not done. Either an exception is thrown or all options are returned. So I don't see the impact of this change here. |
When I set which value-types are allowed they are validated after the normalizing process. Second, the value returned by the normalizer is validated for correctness. Meaning that when I want to return something special the validation needs to be configured to accept the returned value. So technically the normalizer should be run after the validating, instead of running it as first. |
So this change here has nothing to do with #4500 |
Indeed. I have updated the original issue so it will get lost when merging this PR. |
Ah, now your issue is clear to me, @sstok. thanks! I've removed it from the PR description. |
👍 Looks like a bug fix to me. |
To be on the safe side, I'm going to merge this one on master. |
Thank you @wouterj. |
This PR was merged into the 2.6-dev branch. Discussion ---------- [OptionsResolver] Changed order of validation | Q | A | ------------- | --- | Bug fix? | yes | New feature? | yes | BC breaks? | no (I don't think it causes breaks) | Deprecations? | no | Tests pass? | yes | Fixed tickets | | License | MIT | Doc PR | - It's both a new feature and bug fix actually... I let @fabpot decide on this one. <s>@sstok can you please confirm if this fixes #4500 ? I couldn't fully follow that ticket and then I discovered this error. If not, can you please add more information to your ticket about the problems?</s> Commits ------- a4f208b Changed order of validation
It's both a new feature and bug fix actually... I let @fabpot decide on this one.
@sstok can you please confirm if this fixes #4500 ? I couldn't fully followthat ticket and then I discovered this error. If not, can you please add more
information to your ticket about the problems?