-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Utilize {% querystring %} template tag #13638
Copy link
Copy link
Labels
Waiting for: DemandLow priority for development. Pull requests welcome. Can be prioritized by sponsorship.Low priority for development. Pull requests welcome. Can be prioritized by sponsorship.enhancementAdding or requesting a new feature.Adding or requesting a new feature.good first issueOpportunity for newcoming contributors.Opportunity for newcoming contributors.
Metadata
Metadata
Assignees
Labels
Waiting for: DemandLow priority for development. Pull requests welcome. Can be prioritized by sponsorship.Low priority for development. Pull requests welcome. Can be prioritized by sponsorship.enhancementAdding or requesting a new feature.Adding or requesting a new feature.good first issueOpportunity for newcoming contributors.Opportunity for newcoming contributors.
Type
Fields
Give feedbackPriority
None yet
Describe the problem
The querystring handling pagination currently has quite complex logic in
weblate.trans.forms.SearchForm. Most likely it can be fully eliminated by using the{% querystring %}template tag introduced in Django 5.1 (required by Weblate since #13636) see https://docs.djangoproject.com/en/5.1/releases/5.1/#querystring-template-tag.Describe the solution you would like
I believe using
{% querystring %}in the template can replaceitems,urlencodeandreset_offsetmethods in the form.Describe alternatives you have considered
No response
Screenshots
No response
Additional context
weblate/weblate/trans/forms.py
Lines 809 to 852 in b4c476f