-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[Validator] use named-arguments to configure validation constraint options #20596
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
1cbec65
to
83edb8d
Compare
de324eb
to
1d95068
Compare
35d8c97
to
3635154
Compare
11b2c36
to
4f80c5a
Compare
98fa7f2
to
df560bd
Compare
02052a8
to
4520de9
Compare
the PR is now ready to be reviewed |
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.
Wow, thanks a lot Christian for this big effort!
I love this ... but recently I was asked to never use named arguments neither in Symfony Docs nor the Symfony Blog because they can change and BC policy doesn't cover that.
I guess it's OK in this case, but I wanted to point this out. Thanks!
@javiereguiluz We probably need to document somewhere that we guarantee BC for named arguments in attribute class (this does not only apply to validation constraint class but also to e.g. the |
fixes #20589