#11740 closed (fixed)
ModelForm documentation not clear on default attributes of custom Fields
| Reported by: | severian | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.1 |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The current documentation for ModelForm doesn't make clear that when you specify a custom field, default values for
required, initial, etc. will not be drawn from the underlying model, as they are when you let the ModelForm create default fields. A patch is attached that explains this.
As of this writing, the most straightforward example would involve a custom widget, but since a new paradigm for doing that is apparently about to be introduced (http://code.djangoproject.com/ticket/9223), I used an example with a custom field.
A related discussion is here: http://groups.google.com/group/django-developers/browse_thread/thread/904f0ec46525f922.
Attachments (1)
Change History (4)
by , 15 years ago
| Attachment: | modelforms_patch.diff added |
|---|
comment:1 by , 15 years ago
| Triage Stage: | Unreviewed → Ready for checkin |
|---|
comment:2 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:3 by , 15 years ago
Note:
See TracTickets
for help on using tickets.
Documentation patch