Opened 12 years ago
Closed 12 years ago
#21319 closed Cleanup/optimization (fixed)
Document self.fields in forms
| Reported by: | Daniel Greenfeld | Owned by: | Vajrasky Kok |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Normal | Keywords: | forms |
| Cc: | loic@…, sky.kok@… | Triage Stage: | Accepted |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
Instantiated django.forms.Form and django.forms.ModelForm classes have a fields attribute, which is an iterable of the form fields. It's clearly part of the stable API I don't believe it's documented. As it's a critical part of many complex solutions using forms, I think it would be a great addition to the documentation.
Change History (5)
comment:1 by , 12 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|---|
| Type: | Uncategorized → Cleanup/optimization |
comment:2 by , 12 years ago
While we are there - I've seen a number of people struggle with the difference between form.fields and form.base_fields - we should explain what they are (and why you shouldn't mess around with the latter).
comment:3 by , 12 years ago
| Cc: | added |
|---|
comment:4 by , 12 years ago
| Cc: | added |
|---|---|
| Easy pickings: | set |
| Has patch: | set |
| Owner: | changed from to |
| Status: | new → assigned |
| Version: | 1.4 → master |
Here is the PR: https://github.com/django/django/pull/2044
comment:5 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Yes, please.