mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2024-12-22 09:05:43 +00:00
Code Issues 25 Releases Wiki Activity

Fixed #27947 -- Doc'd that model Field.error_messages often don't propagate to forms.

Browse Source
This commit is contained in:
Taavi Teska 2017-04-10 20:24:44 +02:00 committed by Tim Graham
parent e7afef13f5
commit 5dbf1c4b23
2 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
AUTHORS
View File

@ -737,6 +737,7 @@ answer newbie questions, and generally made Django that much better:
Sutrisno Efendi <kangfend@gmail.com>
Swaroop C H <http://www.swaroopch.info>
Szilveszter Farkas <szilveszter.farkas@gmail.com>
Taavi Teska <taaviteska@gmail.com>
Tai Lee <real.human@mrmachine.net>
Takashi Matsuo <matsuo.takashi@gmail.com>
Tareque Hossain <http://www.codexn.com>

3
docs/ref/models/fields.txt
View File

@ -254,6 +254,9 @@ Error message keys include ``null``, ``blank``, ``invalid``, ``invalid_choice``,
``unique``, and ``unique_for_date``. Additional error message keys are
specified for each field in the `Field types`_ section below.
These error messages often don't propagate to forms. See
:ref:`considerations-regarding-model-errormessages`.
``help_text``
-------------