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
minor #28871 [Validator] use constraint options instead of properties (xabbuh)
This PR was merged into the 4.2-dev branch.
Discussion
----------
[Validator] use constraint options instead of properties
| Q | A
| ------------- | ---
| Branch? | master
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets |
| License | MIT
| Doc PR |
For other constraints we always talk about "options" and that's how we name them in the documentation too. I think we should be consistent about the terminology being used here. What do you think?
Commits
-------
f642355 use constraint options instead of properties
Copy file name to clipboardExpand all lines: UPGRADE-4.2.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -261,7 +261,7 @@ TwigBundle
261
261
Validator
262
262
---------
263
263
264
-
* The `checkMX` and `checkHost` properties of the Email constraint are deprecated
264
+
* The `checkMX` and `checkHost` options of the `Email` constraint are deprecated
265
265
* The component is now decoupled from `symfony/translation` and uses `Symfony\Contracts\Translation\TranslatorInterface` instead
266
266
* The `ValidatorBuilderInterface` has been deprecated and `ValidatorBuilder` made final
267
267
* Deprecated validating instances of `\DateTimeInterface` in `DateTimeValidator`, `DateValidator` and `TimeValidator`. Use `Type` instead or remove the constraint if the underlying model is type hinted to `\DateTimeInterface` already.
0 commit comments