minor symfony#33880 [Validator] add notice in UPGRADE file for new Range constraint option (dmaicher)

nicolas-grekas · nicolas-grekas · commit 54ba699eb604 · 2019-10-07T10:30:17.000+02:00
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 symfony#33700 | License | MIT | Doc PR | - There is a change in behavior as mentioned in symfony#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
diff --git a/UPGRADE-4.4.md b/UPGRADE-4.4.md
@@ -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
 -----------------
