#23878: Query object/expression documentation needs to tidied
--------------------------------------+------------------------------------
Reporter: EvilDMP | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by carljm):
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* needs_tests: => 0
* needs_docs: => 0
Comment:
Sounds good to me. I'm not sure the reference documentation for `Prefetch`
should go right into the `prefetch_related` section -- even though it's of
course very closely related, it feels like it complicates the structure of
the document too much to have a full class reference inside a method
reference inside the `QuerySet` class reference. So I might put it at the
bottom of the document, with a link to it. (Similar to the field lookups).
But if you can find a way to do it inline that seems to work OK, great!
--
Ticket URL: <https://code.djangoproject.com/ticket/23878#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.cbc88be79f376087060988a8021a0c10%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
