Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix range filter bug on paging, don't sort on values #67

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

lbrant1
Copy link
Contributor

@lbrant1 lbrant1 commented Oct 16, 2018

Only ignore a key if all it's data is empty. In the case of range
filter, we need to know which value we are filtering on (the greater
than or less than) and it is fine if one of those values is Falsy

Only ignore a key if all it's data is empty. In the case of range
filter, we need to know which value we are filtering on (the greater
than or less than) and it is fine if one of those values is Falsy
seeker/views.py Outdated
parts.extend(urlencode({key: val}) for val in values)
return '&'.join(parts)
pass
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is this here for?

seeker/views.py Outdated
@@ -315,14 +315,11 @@ def normalized_querystring(self, qs=None, ignore=None):
for key in sorted(data):
if ignore and key in ignore:
continue
if not data[key]:
if not data.getlist(key) or not any(data.getlist(key)):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we put "values = data.getlist(key)" above this and just do the "any" check?

… list

Since all items passed in are string values, the only false items would be an empty values list or a a list of empty strings.
@dcwatson
Copy link
Member

Did you mean for this to go into master, or 4.0?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants