#19375: Class-based generic views + pagination hard to understand
-------------------------------------+-------------------------------------
Reporter: vtbassmatt@… | Owner: nobody
Type: | Status: closed
Cleanup/optimization | Version: 1.4
Component: Documentation | Resolution: needsinfo
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: new => closed
* needs_docs: => 0
* resolution: => needsinfo
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
The generic CBV reference docs are always organized with a description,
attributes, methods, and finally context variables.
The "Context" section of the CBV reference docs you're linking to say:
> `page_obj`: An instance of
[https://docs.djangoproject.com/en/1.4/topics/pagination/#django.core.paginator.Page
django.core.paginator.Page]. If the page is not paginated, this context
variable will be `None`.
and if you follow the link to the `Page` class docs you'll see the
description of `has_previous`, `has_next` and friends.
----
Yes, the reference docs for the generic CBVs can be overwhelming, because
these views are built on a rich inheritance scheme and offer lots of
options. But this part doesn't strike me as particularly badly organized
or badly written.
What improvements would you suggest, without breaking the consistency with
the rest of the generic CBV docs?
--
Ticket URL: <https://code.djangoproject.com/ticket/19375#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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
