#22809 closed Cleanup/optimization (fixed)
Refactor model field references
| Reported by: | jorgecarleitao | Owned by: | jorgecarleitao |
|---|---|---|---|
| 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
At the moment, the API references of the model Field are scattered in docs/howto/custom-model-field.txt and docs/ref/models/fields.txt.
I propose to move all the references to docs/ref/models/fields.txt and keep the howto part of the documentation more focused on the subject, e.g. avoiding defining
.. method:: Field.get_prep_value(value)
there.
Change History (10)
comment:1 by , 11 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 11 years ago
| Has patch: | set |
|---|
Pull request: https://github.com/django/django/pull/2796
Both sections of the docs still require a major editorial process on wording and references to models,
either to be addressed in this ticket or another.
comment:3 by , 11 years ago
| Patch needs improvement: | set |
|---|
Please uncheck "Patch needs improvement" when you want me to review it.
comment:4 by , 11 years ago
| Patch needs improvement: | unset |
|---|
comment:6 by , 10 years ago
| Patch needs improvement: | unset |
|---|---|
| Status: | new → assigned |
comment:7 by , 10 years ago
| Patch needs improvement: | set |
|---|
Still has some problems and doesn't merge cleanly.
comment:8 by , 10 years ago
| Patch needs improvement: | unset |
|---|
Fixed the problems and rebased against master.
comment:9 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
Yes, probably at the bottom of the page in their own section sounds good.