#10941: Add querystring helper methods to Page class
------------------------------+------------------------------------
Reporter: benspaulding | Owner: nobody
Type: New feature | Status: new
Component: Core (Other) | Version: master
Severity: Normal | Resolution:
Keywords: pagination | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Comment (by benspaulding):
Replying to [comment:9 apollo13]:
> Oh yeah, I run into this all the time. I think that we should allow
customization of the querystring name, eg 'p' instead of 'page'. To that
end a simple filter and/or tag might be better.
Just to be clear, drop the helper methods and go with a filter or tag,
requiring use of the {{{django.core.context_processors.request}}}? (Sounds
fine to me, I just want to be clear on the recommended route so this
doesn’t bog down in implementation.) What template tag library would that
live in? There doesn’t seem to be a current contrib app it would fit in,
and I am not sure it belongs in built-ins if it depends on a context
processor that is not installed by default.
--
Ticket URL: <https://code.djangoproject.com/ticket/10941#comment:10>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
