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 #33880 [Validator] add notice in UPGRADE file for new Range constraint option (dmaicher)
This PR was merged into the 4.4 branch.
Discussion
----------
[Validator] add notice in UPGRADE file for new Range constraint option
| Q | A
| ------------- | ---
| Branch? | 4.4
| Bug fix? | no
| New feature? | no
| Deprecations? | no
| Tickets | Fix#33700
| License | MIT
| Doc PR | -
There is a change in behavior as mentioned in #33700 that causes small issues on one of my apps. I only noticed it because of a test fail.
Instead of reverting this nice feature I propose to document it in the UPGRADE file so that people are aware of it.
Commits
-------
d4ab35c [Validator] add notice in UPGRADE file for new Range constraint option
Copy file name to clipboardExpand all lines: UPGRADE-4.4.md
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -344,6 +344,8 @@ Validator
344
344
* Overriding the methods `ConstraintValidatorTestCase::setUp()` and `ConstraintValidatorTestCase::tearDown()` without the `void` return-type is deprecated.
345
345
* deprecated `Symfony\Component\Validator\Mapping\Cache\CacheInterface` and all implementations in favor of PSR-6.
346
346
* deprecated `ValidatorBuilder::setMetadataCache`, use `ValidatorBuilder::setMappingCache` instead.
347
+
* The `Range` constraint has a new message option `notInRangeMessage` that is used when both `min` and `max` values are set.
348
+
In case you are using custom translations make sure to add one for this new message.
0 commit comments