summaryrefslogtreecommitdiff
path: root/docs/_ext/djangodocs.py
diff options
context:
space:
mode:
authorLoic Bistuer <loic.bistuer@sixmedia.com>2013-10-14 20:45:30 +0700
committerTim Graham <timograham@gmail.com>2013-10-14 10:54:22 -0400
commit54cd930baf49c45e3e91338a9f4a56d19090ff25 (patch)
tree8bf14301a858109f8e7eca6443103673f1a92c79 /docs/_ext/djangodocs.py
parent9b7d38ed5a9eed21c496abb1b874cfe53da9c9c9 (diff)
downloaddjango-54cd930baf49c45e3e91338a9f4a56d19090ff25.tar.gz
Clarfied the ModelForm docs with respect to generated vs. declared fields.
The ModelForm docs suggested that fields defined declaratively override default fields generated from the form Meta. This is conceptually wrong, especially with inheritance in mind. Meta is usually defined on the topmost ModelForm subclass, while fields can come from anywhere in the MRO, especially base classes; therefore we suggested that something defined in a base class override something from a subclass. This patch rephrases the docs around the idea that Meta is used to generate *missing* fields. Refs #8620, #19617. Thanks @mjtamlyn and @timgraham for the review.
Diffstat (limited to 'docs/_ext/djangodocs.py')
0 files changed, 0 insertions, 0 deletions