#7983 closed (fixed)
ModelAdmin's `fields` option is undocumented
| Reported by: | Julien Phalip | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The Admin documentation is missing a description for the ModelAdmin's fields option. At the moment, only fieldsets is described.
[1] http://www.djangoproject.com/documentation/admin/#modeladmin-options
Attachments (1)
Change History (8)
comment:1 by , 16 years ago
| Component: | Uncategorized → Documentation |
|---|
comment:2 by , 16 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:3 by , 16 years ago
| Resolution: | invalid |
|---|---|
| Status: | closed → reopened |
The fields element of the field_options dictionary within a fieldsets specification is documented.
Fields as a ModelAdmin option (an alternative to fieldsets) is not, near as I can tell. If it is there somewhere it ought to have a place in the contents list on the right, and it doesn't. If I'm missing the overall description that contents list item at least should be added, so it can be found. Searching on 'fields' on that page returns rather a lot of hits.
comment:4 by , 16 years ago
Karen and mrts, I confirm that I meant fields as the alternative for fieldsets, not the dictionary key within the fieldsets option.
I attached a simple patch which hopefully is clear enough.
by , 16 years ago
| Attachment: | 7983.fields_doc.diff added |
|---|
comment:5 by , 16 years ago
| Has patch: | set |
|---|
comment:6 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Please check things carefully before you open tickets. Both
fieldsandfieldsetsare documented on the URL you gave.