#7986 closed (fixed)
Documentation for prepopulated_fields isn't very clear
| Reported by: | Fraser Nevett | 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
Presently, the prepopulated_fields documentation doesn't really say what prepopulated_fields actually does. Specifically, it doesn't mention that it is designed for use with SlugFields.
Pre-NFA, this functionality was enabled by the prepoulate_from argument in SlugField. This tight-coupling made what it does more obvious.
I'll attach a patch to clarify the documentation.
Attachments (1)
Change History (3)
by , 16 years ago
| Attachment: | 7986.patch added |
|---|
comment:1 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
(In [8109]) Fixed #7986 -- Added to the documentation the purpose of the
prepopulated_fieldsModelAdminoption now that its no longer just a parameter forSlugFieldfields, thanks frasern.