mirror of
https://github.com/django/django.git
synced 2025-08-31 15:57:45 +00:00
Fixed #23151 -- Deprecated RegexField.error_message.
Thanks Baptiste Mispelon for the suggestion.
This commit is contained in:
parent
44169a00c1
commit
0f2ceee025
6 changed files with 31 additions and 8 deletions
|
@ -805,10 +805,13 @@ For each field, we describe the default widget used if you don't specify
|
|||
Also takes ``max_length`` and ``min_length``, which work just as they do for
|
||||
``CharField``.
|
||||
|
||||
The optional argument ``error_message`` is also accepted for backwards
|
||||
compatibility. The preferred way to provide an error message is to use the
|
||||
``error_messages`` argument, passing a dictionary with ``'invalid'`` as a key
|
||||
and the error message as the value.
|
||||
.. deprecated:: 1.8
|
||||
|
||||
The optional argument ``error_message`` is also accepted for backwards
|
||||
compatibility but will be removed in Django 2.0. The preferred way to
|
||||
provide an error message is to use the :attr:`~Field.error_messages`
|
||||
argument, passing a dictionary with ``'invalid'`` as a key and the error
|
||||
message as the value.
|
||||
|
||||
``SlugField``
|
||||
~~~~~~~~~~~~~
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue