diff options
| author | Markus Holtermann <info@markusholtermann.eu> | 2014-09-24 19:08:45 +0200 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-09-24 14:32:49 -0400 |
| commit | c692e37b6350171ee2e04b3e7090babf34ac140b (patch) | |
| tree | 097544d991582cbaa2786bfe31561ce2eac132a7 /docs/ref | |
| parent | 066e672d79ceb416ac87e51c8fa400221fa8604f (diff) | |
Fixed #22959 -- Documented that class-based validators need to be deconstructible.
Diffstat (limited to 'docs/ref')
| -rw-r--r-- | docs/ref/validators.txt | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/ref/validators.txt b/docs/ref/validators.txt index 42fb44b650..260c066151 100644 --- a/docs/ref/validators.txt +++ b/docs/ref/validators.txt @@ -37,6 +37,14 @@ use the same validator with forms:: class MyForm(forms.Form): even_field = forms.IntegerField(validators=[validate_even]) +You can also use a class with a ``__call__()`` method for more complex or +configurable validators. :class:`RegexValidator`, for example, uses this +technique. If a class-based validator is used in the +:attr:`~django.db.models.Field.validators` model field option, you should make +sure it is :ref:`serializable by the migration framework +<migration-serializing>` by adding :ref:`deconstruct() +<custom-deconstruct-method>` and ``__eq__()`` methods. + How validators are run ====================== |