diff options
| author | Loic Bistuer <loic.bistuer@gmail.com> | 2014-11-05 16:00:22 +0700 |
|---|---|---|
| committer | Loic Bistuer <loic.bistuer@gmail.com> | 2014-11-05 16:00:30 +0700 |
| commit | f1f0c4f16bd7a1138a881c3645719e84e200440a (patch) | |
| tree | d3a5638c8396b4c2df999a72ccf2b4d28bc1803d /docs/ref/forms | |
| parent | 81477c91f68d7091f8da417a030dd4b9b776b70a (diff) | |
Removed confusing paragraph from the docs.
This snippet wasn't particularly helpful as `add_error()` is described
in greater details in the following section.
Thanks Claude Paroz for the report.
Diffstat (limited to 'docs/ref/forms')
| -rw-r--r-- | docs/ref/forms/validation.txt | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/docs/ref/forms/validation.txt b/docs/ref/forms/validation.txt index d2d20fb6fe..3ff2ea0ab7 100644 --- a/docs/ref/forms/validation.txt +++ b/docs/ref/forms/validation.txt @@ -326,13 +326,6 @@ write a cleaning method that operates on the ``recipients`` field, like so:: # not. return data -Sometimes you may want to add an error message to a particular field from the -form's :meth:`~Form.clean()` method, in which case you can use -:meth:`~django.forms.Form.add_error()`. Note that this won't always be -appropriate and the more typical situation is to raise a ``ValidationError`` -from , which is turned into a form-wide error that is available through the -:meth:`Form.non_field_errors() <django.forms.Form.non_field_errors>` method. - .. _validating-fields-with-clean: Cleaning and validating fields that depend on each other |
