[hibernate-commits] [hibernate/hibernate-validator] 5ff7c6: HV-1614 Add check if the container element context...
Branch: refs/heads/6.0
Home: https://github.com/hibernate/hibernate-validator
Commit: 5ff7c64e95c01b46ecd094f38312bc602bd10693
https://github.com/hibernate/hibernate-validator/commit/5ff7c64e95c01b46e...
Author: marko-bekhta <marko.prykladna(a)gmail.com>
Date: 2018-05-09 (Wed, 09 May 2018)
Changed paths:
M
engine/src/main/java/org/hibernate/validator/internal/cfg/context/CascadableConstraintMappingContextImplBase.java
M
engine/src/main/java/org/hibernate/validator/internal/cfg/context/ContainerElementConstraintMappingContextImpl.java
M
engine/src/test/java/org/hibernate/validator/test/cfg/ProgrammaticContainerElementConstraintsForFieldTest.java
Log Message:
-----------
HV-1614 Add check if the container element context exists when adding a nested type
argument constraints programmatically
Rather than simply put a new context into the map we need to check if there's one
already created by any previous calls. This might happen when someone wants to add
constraints for different type arguments of a nested container.
**NOTE:** This service been marked for deprecation:
https://developer.github.com/changes/2018-04-25-github-services-deprecation/
Functionality will be removed from GitHub.com on January 31st, 2019.