#19887 closed Cleanup/optimization (fixed)
ModelAdmin.fields and ModelAdmin.fieldset not very detailed documented
| Reported by: | Owned by: | Zbigniew Siciarz | |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
ModelAdmin.fields and ModelAdmin.fieldset are not very detailed documented compared to ModelAdmin.display_list. It is not clear if only fields or callables too can be used, and how to do so. In fact, callables need to be in readonly_fields, which is quite logical after you found out, but no hint is given in the documentation.
This could be presented in comparison to the "list" display properties, where you have to state so if you want to make fields editable.
Maybe noteworth is some hint about callables that you want to make writable. I guess in that case a custom Field would be the Right Thing (?).
Change History (7)
comment:1 by , 12 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|---|
| Type: | Uncategorized → New feature |
comment:2 by , 12 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 12 years ago
| Version: | 1.4 → master |
|---|
comment:4 by , 12 years ago
| Has patch: | set |
|---|---|
| Type: | New feature → Cleanup/optimization |
Relevant pull request: https://github.com/django/django/pull/762
comment:5 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:7 by , 12 years ago
Wow, now I'm impressed by the fast reaction!
Thanks, and keep up the fine work!
I've noticed this omission before; I think it would be reasonable for the
fields/fieldsetsdocumentation to make some note of what non-fields are allowed and under what circumstances.