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
Copy file name to clipboardExpand all lines: src/main/asciidoc/1. introduction.adoc
+14-2Lines changed: 14 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,9 +3,21 @@
3
3
The Cascade Validation Plugin provides a small, focused extension to Grails constraints that makes it easy to validate associated objects (domain associations or command object) as part of normal validation.
4
4
Instead of manually calling validate() on every association, the plugin supplies a constraint (see usage) that marks an association to be validated automatically.
5
5
6
-
== Breaking change.
6
+
== Breaking changes.
7
7
8
8
Due to a change in Hibernate, there is a name clash with the `cascade` constraint keyword.
9
9
For this reason `cascade` was renamed to `cascaded`.
10
10
Please update all your domain and command classes accordingly.
11
-
Search for `cascade: true` (or `cascade: false`) and replace with `cascaded: true` (or `false`).
11
+
Search for `cascade: true` (or `cascade: false`) and replace with `cascaded: true` (or `false`).
12
+
13
+
The constraint class was renamed from `CascadeConstraint` to `CascadedConstraint` and the registration class from `CascadeConstraintRegistration` to `CascadedConstraintRegistration`
14
+
15
+
The previous format for the `field` name on collections was `field.0.childProperty`, but since
16
+
Grails 7 does cascade validations on Domain objects, and the format for errors in this validation is `field[0].childProperty` a configuration property was added, to control if the legacy format should be used, or if the new format is used:
When binding data to `grails.validation.Validateable` objects (e.g., via controllers or REST endpoints), call `validate()` or rely on automatic validation in data-binding flows, the `CascadeConstraint` ensures marked associations are validated as part of the root object validation.
70
+
When binding data to `grails.validation.Validateable` objects (e.g., via controllers or REST endpoints), call `validate()` or rely on automatic validation in data-binding flows, the `CascadedConstraint` ensures marked associations are validated as part of the root object validation.
0 commit comments