mirror of
https://github.com/django/django.git
synced 2025-10-17 22:07:29 +00:00
Adapted uses of versionchanged/versionadded to the new form.
Refs #20104.
This commit is contained in:
parent
1ddeeb5b8e
commit
78c842a323
48 changed files with 206 additions and 148 deletions
|
@ -468,6 +468,7 @@ For each field, we describe the default widget used if you don't specify
|
|||
``%(limit_value)s``, which will be substituted by the appropriate limit.
|
||||
|
||||
.. versionchanged:: 1.6
|
||||
|
||||
Similarly, the ``max_digits``, ``max_decimal_places`` and
|
||||
``max_whole_digits`` error messages may contain ``%(max)s``.
|
||||
|
||||
|
@ -1014,10 +1015,12 @@ objects (in the case of ``ModelMultipleChoiceField``) into the
|
|||
``invalid_pk_value``
|
||||
|
||||
.. versionchanged:: 1.5
|
||||
|
||||
The empty and normalized values were changed to be consistently
|
||||
``QuerySets`` instead of ``[]`` and ``QuerySet`` respectively.
|
||||
|
||||
.. versionchanged:: 1.6
|
||||
|
||||
The ``invalid_choice`` message may contain ``%(value)s`` and the
|
||||
``invalid_pk_value`` message may contain ``%(pk)s``, which will be
|
||||
substituted by the appropriate values.
|
||||
|
|
|
@ -42,7 +42,7 @@ Model Form Functions
|
|||
|
||||
.. versionchanged:: 1.6
|
||||
|
||||
The ``widgets`` and the ``validate_max`` parameters were added.
|
||||
The ``widgets`` and the ``validate_max`` parameters were added.
|
||||
|
||||
.. function:: inlineformset_factory(parent_model, model, form=ModelForm, formset=BaseInlineFormSet, fk_name=None, fields=None, exclude=None, extra=3, can_order=False, can_delete=True, max_num=None, formfield_callback=None, widgets=None, validate_max=False)
|
||||
|
||||
|
@ -57,4 +57,4 @@ Model Form Functions
|
|||
|
||||
.. versionchanged:: 1.6
|
||||
|
||||
The ``widgets`` and the ``validate_max`` parameters were added.
|
||||
The ``widgets`` and the ``validate_max`` parameters were added.
|
||||
|
|
|
@ -359,7 +359,7 @@ considering aren't valid, we must remember to remove them from the
|
|||
|
||||
.. versionchanged:: 1.5
|
||||
|
||||
Django used to remove the ``cleaned_data`` attribute entirely if there were
|
||||
any errors in the form. Since version 1.5, ``cleaned_data`` is present even if
|
||||
the form doesn't validate, but it contains only field values that did
|
||||
validate.
|
||||
Django used to remove the ``cleaned_data`` attribute entirely if there were
|
||||
any errors in the form. Since version 1.5, ``cleaned_data`` is present even if
|
||||
the form doesn't validate, but it contains only field values that did
|
||||
validate.
|
||||
|
|
|
@ -522,6 +522,7 @@ Selector and checkbox widgets
|
|||
``True`` if the checkbox should be checked for that value.
|
||||
|
||||
.. versionchanged:: 1.5
|
||||
|
||||
Exceptions from ``check_test`` used to be silenced by its caller,
|
||||
this is no longer the case, they will propagate upwards.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue