mirror of
https://github.com/django/django.git
synced 2025-08-04 10:59:45 +00:00
Fixed #30573 -- Rephrased documentation to avoid words that minimise the involved difficulty.
This patch does not remove all occurrences of the words in question. Rather, I went through all of the occurrences of the words listed below, and judged if they a) suggested the reader had some kind of knowledge/experience, and b) if they added anything of value (including tone of voice, etc). I left most of the words alone. I looked at the following words: - simply/simple - easy/easier/easiest - obvious - just - merely - straightforward - ridiculous Thanks to Carlton Gibson for guidance on how to approach this issue, and to Tim Bell for providing the idea. But the enormous lion's share of thanks go to Adam Johnson for his patient and helpful review.
This commit is contained in:
parent
addabc492b
commit
4a954cfd11
149 changed files with 1101 additions and 1157 deletions
|
@ -569,8 +569,8 @@ Adding additional fields to a formset
|
|||
|
||||
If you need to add additional fields to the formset this can be easily
|
||||
accomplished. The formset base class provides an ``add_fields`` method. You
|
||||
can simply override this method to add your own fields or even redefine the
|
||||
default fields/attributes of the order and deletion fields::
|
||||
can override this method to add your own fields or even redefine the default
|
||||
fields/attributes of the order and deletion fields::
|
||||
|
||||
>>> from django.forms import BaseFormSet
|
||||
>>> from django.forms import formset_factory
|
||||
|
@ -651,9 +651,9 @@ This is useful if you want to :ref:`use more than one formset in a view
|
|||
Using a formset in views and templates
|
||||
======================================
|
||||
|
||||
Using a formset inside a view is as easy as using a regular ``Form`` class.
|
||||
The only thing you will want to be aware of is making sure to use the
|
||||
management form inside the template. Let's look at a sample view::
|
||||
Using a formset inside a view is not very different from using a regular
|
||||
``Form`` class. The only thing you will want to be aware of is making sure to
|
||||
use the management form inside the template. Let's look at a sample view::
|
||||
|
||||
from django.forms import formset_factory
|
||||
from django.shortcuts import render
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue