Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
Removed @internal from Composite#37558
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
nicolas-grekas commentedJul 12, 2020
/cc@ogizanagi maybe? |
ogizanagi commentedJul 15, 2020
I don't have arguments against. What do you think@xabbuh? |
xabbuh commentedJul 16, 2020
works for me |
ogizanagi left a comment
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.
What about targeting 5.1?
f180fd3 to8958ce1Comparefabpot commentedJul 23, 2020
Thank you@vudaltsov. |
I think that Composite should not be@internal. Even with the new@Compound constraint Composite is still useful for complex custom validators.
For example, I have @ExcelColumn(string $column, array $constraints) that checks that all cells in a column of an uploaded Excel file are valid. This cannot be expressed with@Compound.