Skip to content

[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

Merged
merged 1 commit into from
Jan 24, 2025

Conversation

xabbuh
Copy link
Member

@xabbuh xabbuh commented Jan 24, 2025

fixes #20589

@carsonbot carsonbot added this to the 7.3 milestone Jan 24, 2025
@xabbuh xabbuh changed the title use named-arguments to configure validation constraint options [WIP][Validator] use named-arguments to configure validation constraint options Jan 24, 2025
@carsonbot carsonbot changed the title [WIP][Validator] use named-arguments to configure validation constraint options [WIP] use named-arguments to configure validation constraint options Jan 24, 2025
@carsonbot carsonbot changed the title [WIP] use named-arguments to configure validation constraint options [Validator] [WIP] use named-arguments to configure validation constraint options Jan 24, 2025
@xabbuh xabbuh force-pushed the issue-20589 branch 9 times, most recently from 1cbec65 to 83edb8d Compare January 24, 2025 10:29
@xabbuh xabbuh changed the title [Validator] [WIP] use named-arguments to configure validation constraint options [Validator] use named-arguments to configure validation constraint options Jan 24, 2025
@xabbuh xabbuh force-pushed the issue-20589 branch 2 times, most recently from de324eb to 1d95068 Compare January 24, 2025 10:58
@xabbuh xabbuh force-pushed the issue-20589 branch 2 times, most recently from 35d8c97 to 3635154 Compare January 24, 2025 11:07
@xabbuh xabbuh changed the title [Validator] use named-arguments to configure validation constraint options [WIP][Validator] use named-arguments to configure validation constraint options Jan 24, 2025
@xabbuh xabbuh force-pushed the issue-20589 branch 3 times, most recently from 11b2c36 to 4f80c5a Compare January 24, 2025 11:15
@xabbuh xabbuh force-pushed the issue-20589 branch 6 times, most recently from 98fa7f2 to df560bd Compare January 24, 2025 11:27
@xabbuh xabbuh changed the title [WIP][Validator] use named-arguments to configure validation constraint options [Validator] use named-arguments to configure validation constraint options Jan 24, 2025
@xabbuh xabbuh force-pushed the issue-20589 branch 2 times, most recently from 02052a8 to 4520de9 Compare January 24, 2025 11:32
@xabbuh
Copy link
Member Author

xabbuh commented Jan 24, 2025

the PR is now ready to be reviewed

Copy link
Member

@javiereguiluz javiereguiluz left a 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!

@xabbuh
Copy link
Member Author

xabbuh commented Jan 24, 2025

@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 Route attribute and attributes provided by the Serializer component).

@xabbuh xabbuh merged commit faa9c32 into symfony:7.3 Jan 24, 2025
3 checks passed
@xabbuh xabbuh deleted the issue-20589 branch January 24, 2025 19:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants