diff options
| author | Natalia <124304+nessita@users.noreply.github.com> | 2025-08-22 12:36:48 -0300 |
|---|---|---|
| committer | nessita <124304+nessita@users.noreply.github.com> | 2025-08-25 10:51:10 -0300 |
| commit | 4286a23df64f6ce3b9b6ed097f4d1aac7d9e0de4 (patch) | |
| tree | e7225d1586c174b5945f595b3759b7c6dddbdae1 /docs/ref/forms | |
| parent | 01a460f23e470555a733b8980401402b7947bb9f (diff) | |
Refs #36485 -- Removed double spaces after periods in sentences.
Diffstat (limited to 'docs/ref/forms')
| -rw-r--r-- | docs/ref/forms/api.txt | 4 | ||||
| -rw-r--r-- | docs/ref/forms/fields.txt | 18 |
2 files changed, 11 insertions, 11 deletions
diff --git a/docs/ref/forms/api.txt b/docs/ref/forms/api.txt index 399c8f3728..ed2bb4d604 100644 --- a/docs/ref/forms/api.txt +++ b/docs/ref/forms/api.txt @@ -842,7 +842,7 @@ By default, the form rendering methods include: It's always a good idea to use ``<label>`` tags. The ``id`` attribute values are generated by prepending ``id_`` to the form -field names. This behavior is configurable, though, if you want to change the +field names. This behavior is configurable, though, if you want to change the ``id`` convention or remove HTML ``id`` attributes and ``<label>`` tags entirely. @@ -1389,7 +1389,7 @@ Methods of ``BoundField`` .. method:: BoundField.as_widget(widget=None, attrs=None, only_initial=False) Renders the field by rendering the passed widget, adding any HTML - attributes passed as ``attrs``. If no widget is specified, then the + attributes passed as ``attrs``. If no widget is specified, then the field's default widget will be used. ``only_initial`` is used by Django internals and should not be set diff --git a/docs/ref/forms/fields.txt b/docs/ref/forms/fields.txt index b09a43f47c..f0a8e6c341 100644 --- a/docs/ref/forms/fields.txt +++ b/docs/ref/forms/fields.txt @@ -713,15 +713,15 @@ For each field, we describe the default widget used if you don't specify .. attribute:: allow_files - Optional. Either ``True`` or ``False``. Default is ``True``. Specifies - whether files in the specified location should be included. Either this or - :attr:`allow_folders` must be ``True``. + Optional. Either ``True`` or ``False``. Default is ``True``. Specifies + whether files in the specified location should be included. Either this + or :attr:`allow_folders` must be ``True``. .. attribute:: allow_folders - Optional. Either ``True`` or ``False``. Default is ``False``. Specifies - whether folders in the specified location should be included. Either this or - :attr:`allow_files` must be ``True``. + Optional. Either ``True`` or ``False``. Default is ``False``. Specifies + whether folders in the specified location should be included. Either + this or :attr:`allow_files` must be ``True``. ``FloatField`` @@ -1217,7 +1217,7 @@ Slightly complex built-in ``Field`` classes .. attribute:: fields A tuple of fields whose values are cleaned and subsequently combined - into a single value. Each value of the field is cleaned by the + into a single value. Each value of the field is cleaned by the corresponding field in ``fields`` -- the first value is cleaned by the first field, the second value is cleaned by the second field, etc. Once all fields are cleaned, the list of clean values is combined into @@ -1325,9 +1325,9 @@ Fields which handle relationships Two fields are available for representing relationships between models: :class:`ModelChoiceField` and -:class:`ModelMultipleChoiceField`. Both of these fields require a +:class:`ModelMultipleChoiceField`. Both of these fields require a single ``queryset`` parameter that is used to create the choices for -the field. Upon form validation, these fields will place either one +the field. Upon form validation, these fields will place either one model object (in the case of ``ModelChoiceField``) or multiple model objects (in the case of ``ModelMultipleChoiceField``) into the ``cleaned_data`` dictionary of the form. |