You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Please read the text in context of the part "how to reproduce".
In Symfony 4.2.5, it was not necessary to add the Valid-Constraint to a list to get the objects in this list to be validated (e.g. would result in a NotNull-Violation, if the name was null). In 4.2.6 this is now necessary.
I didn't found anything about this behavior-change. Therefore i searched the documentation, the UPGRADE- and CHANGELOG-files and the tests in the validator-component. Also i don't know, whether this should be handled as a BC-break or a Bugfix (as it always was necessary to use the Valid-Constraint, if the relation was 1:1).
The text was updated successfully, but these errors were encountered:
rejinka
changed the title
[Validator] Handling of lists slightly changed from 4.2 to 4.3
[Validator] Handling of lists slightly changed from 4.2.5 to 4.2.6
Oct 8, 2019
Symfony version(s) affected: >=4.2.6,>=4.3.0
Description
Please read the text in context of the part "how to reproduce".
In Symfony 4.2.5, it was not necessary to add the Valid-Constraint to a list to get the objects in this list to be validated (e.g. would result in a NotNull-Violation, if the name was null). In 4.2.6 this is now necessary.
I didn't found anything about this behavior-change. Therefore i searched the documentation, the UPGRADE- and CHANGELOG-files and the tests in the validator-component. Also i don't know, whether this should be handled as a BC-break or a Bugfix (as it always was necessary to use the Valid-Constraint, if the relation was 1:1).
How to reproduce
The text was updated successfully, but these errors were encountered: