[Validator] fall back to legacy options handling if configured named arguments do not match #61617
Conversation
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
xabbuh
commented
Sep 3, 2025
| } | ||
|
|
||
| if (array_is_list($options)) { | ||
| if (array_is_list($options) || isset($options['value'])) { |
Member
Author
There was a problem hiding this comment.
This might be a bit risky if the constraint has a constructor argument named $value.
An alternative solution would be wrapping the call further down in a try catch block like this:
try {
return new $className(...$options);
} catch (\Error $e) {
if (str_starts_with($e->getMessage(), 'Unknown named parameter')) {
return new $className($options);
}
throw $e;
}
Member
Author
There was a problem hiding this comment.
in any case, we should deprecate this in 7.4 after merging up
Member
There was a problem hiding this comment.
let's do it the safest way?
xabbuh
changed the title
Member
|
Thank you @xabbuh. |
Member
|
Thanks! Follow up welcome on 7.4 🙏 |
Member
Author
|
the follow-up PR for the deprecation is here: #61791 |
nicolas-grekas
added a commit
that referenced
this pull request
Sep 24, 2025
… in YAML/XML mapping files (xabbuh) This PR was merged into the 7.4 branch. Discussion ---------- [Validator] deprecate implicit constraint option names in YAML/XML mapping files | Q | A | ------------- | --- | Branch? | 7.4 | Bug fix? | no | New feature? | no | Deprecations? | yes | Issues | see #61617 (comment) | License | MIT Commits ------- 14ca8ac deprecate implicit constraint option names in YAML/XML mapping files
symfony-splitter
pushed a commit
to symfony/validator
that referenced
this pull request
Sep 24, 2025
… in YAML/XML mapping files (xabbuh) This PR was merged into the 7.4 branch. Discussion ---------- [Validator] deprecate implicit constraint option names in YAML/XML mapping files | Q | A | ------------- | --- | Branch? | 7.4 | Bug fix? | no | New feature? | no | Deprecations? | yes | Issues | see symfony/symfony#61617 (comment) | License | MIT Commits ------- 14ca8ac7dcc deprecate implicit constraint option names in YAML/XML mapping files
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
generalized alternative to #61613