The GitHub Actions job "CI" on grails-core.git/fix/gorm-bean-validation-constraints has succeeded. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: 15689b8f9f4ca69a0269688b046c9c26c7fd0f10 / James Daugherty <[email protected]> Validate each instance, proxies, transient @Valid properties and sequences as Bean Validation does The visited set of PersistentEntityValidator compares instances by identity, so an associated instance equal to one already validated, as a Comparable sorting alike or an entity with the same business key is, is validated as well. supports() accepts the subclasses of the entity, such as the class of a proxy, and validate() unwraps a proxy to validate the instance behind it. validate() validates the block, then the new validateAssociationsAndBeyond hook cascades and validates beyond the constraints, which the Jakarta validator overrides to validate a group sequence group by group over the whole graph, stopping at the first group with a violation anywhere in it, as Hibernate Validator does. An association marked @Valid passes an unconverted group alone, without the groups it extends that a conversion converted, through an ExcludedGroups hint the adapter filters the reported violations by. The traversable resolver lets the provider cascade through the properties marked @Valid that are not persistent associations, such as a transient one. The translator leaves out the constraints composing a @ConstraintComposition other than AND. The registry asks the provider whether an entity is bean constrained, so a subclass inheriting its annotations, a class with a class level constraint alone and an owner carrying only @Valid and @ConvertGroup get the Jakarta validator, in DataTest as well. The guide and the upgrade note cover each change. Report URL: https://github.com/apache/grails-core/actions/runs/40908809760 With regards, GitHub Actions via GitBox
