Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 3250ed4

Browse filesBrowse files
committed
Revert "Fixed wrong inheritance information"
This reverts commit 6c3ff5e.
1 parent 7dd450e commit 3250ed4
Copy full SHA for 3250ed4

File tree

1 file changed

+5
-5
lines changed
Filter options

1 file changed

+5
-5
lines changed

‎validation/groups.rst

Copy file name to clipboardExpand all lines: validation/groups.rst
+5-5Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -166,11 +166,11 @@ the class name or the string ``Default``.
166166
object that's actually the one being validated.
167167

168168
If you have inheritance (e.g. ``User extends BaseUser``) and you validate
169-
with the class name of the subclass (i.e. ``User``), then only constraints
170-
in the ``User`` will be validated. To validate the parent constraints as
171-
  well you need to provide multiple groups (i.e ``User`` and ``BaseUser``) or
172-
   ``Default``.
173-
169+
with the class name of the subclass (i.e. ``User``), then all constraints
170+
in the ``User`` and ``BaseUser`` will be validated. However, if you
171+
validate using the base class (i.e. ``BaseUser``), then only the default
172+
constraints in the ``BaseUser`` class will be validated.
173+
174174
To tell the validator to use a specific group, pass one or more group names
175175
as the third argument to the ``validate()`` method::
176176

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.