diff options
| author | antoliny0919 <antoliny0919@gmail.com> | 2024-11-16 11:12:51 +0900 |
|---|---|---|
| committer | Sarah Boyce <42296566+sarahboyce@users.noreply.github.com> | 2024-11-18 17:00:56 +0100 |
| commit | 4c65aecfe7ebebf2c90f2cccb6d240cd14c1445c (patch) | |
| tree | 41dad519f6b3b39026f32aa09de1bb22d34db72a | |
| parent | 1be9c5fb56febbf63072c81f61664f25b6c16bc0 (diff) | |
[5.1.x] Refs #32339 -- Updated formset docs to reflect default rendering as as_div.
Backport of c56e1273a9d87ffad3a84fb597550f79b9820281 from main.
| -rw-r--r-- | docs/topics/forms/formsets.txt | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/topics/forms/formsets.txt b/docs/topics/forms/formsets.txt index 3b68ed614c..14d4962eb6 100644 --- a/docs/topics/forms/formsets.txt +++ b/docs/topics/forms/formsets.txt @@ -1005,10 +1005,11 @@ deal with the management form: The above ends up calling the :meth:`BaseFormSet.render` method on the formset class. This renders the formset using the template specified by the :attr:`~BaseFormSet.template_name` attribute. Similar to forms, by default the -formset will be rendered ``as_table``, with other helper methods of ``as_p`` -and ``as_ul`` being available. The rendering of the formset can be customized -by specifying the ``template_name`` attribute, or more generally by -:ref:`overriding the default template <overriding-built-in-formset-templates>`. +formset will be rendered ``as_div``, with other helper methods of ``as_p``, +``as_ul``, and ``as_table`` being available. The rendering of the formset can +be customized by specifying the ``template_name`` attribute, or more generally +by :ref:`overriding the default template +<overriding-built-in-formset-templates>`. .. _manually-rendered-can-delete-and-can-order: |