#26322 closed Cleanup/optimization (fixed)
Rewrite the lazy model reference section of related fields docs
| Reported by: | Simon Charette | Owned by: | Clifford Gama |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Normal | 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
This is follow up of the lazy operation refactor (#24215) that was initially thought to have introduced a regression in Django 1.9 (#25858) which ended up being a feature (#26186) people relied on since at least Django 1.2.
During the discussion about the behavior of app relative model reference defined on abstract models it was suggested the documentation should be revised to detail how ''recursive'', ''relative'' and ''absolute'' string references work and go on to explain how they work in an abstract context.
Change History (8)
comment:1 by , 9 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 3 months ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 2 months ago
| Has patch: | set |
|---|
comment:4 by , 2 months ago
| Patch needs improvement: | set |
|---|
Added some small review comments, PR is looking great!
comment:5 by , 2 months ago
| Patch needs improvement: | unset |
|---|
comment:6 by , 2 months ago
| Triage Stage: | Accepted → Ready for checkin |
|---|
Note:
See TracTickets
for help on using tickets.
PR