diogo
/
symfony
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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 https://github.com/symfony/symfony/issues/33700
| License       | MIT
| Doc PR        | -

There is a change in behavior as mentioned in https://github.com/symfony/symfony/issues/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
-------

d4ab35cfab [Validator] add notice in UPGRADE file for new Range constraint option
This commit is contained in:
Nicolas Grekas 2019-10-07 10:30:17 +02:00
parent 3a66d59326 d4ab35cfab
commit 54ba699eb6
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
UPGRADE-4.4.md
View File

@ -344,6 +344,8 @@ Validator
* Overriding the methods `ConstraintValidatorTestCase::setUp()` and `ConstraintValidatorTestCase::tearDown()` without the `void` return-type is deprecated.
* deprecated `Symfony\Component\Validator\Mapping\Cache\CacheInterface` and all implementations in favor of PSR-6.
* deprecated `ValidatorBuilder::setMetadataCache`, use `ValidatorBuilder::setMappingCache` instead.
* The `Range` constraint has a new message option `notInRangeMessage` that is used when both `min` and `max` values are set.
In case you are using custom translations make sure to add one for this new message.
WebProfilerBundle
-----------------