Skip to content

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

Open
lbrant1 wants to merge 3 commits into
imsweb:masterfrom
lbrant1:range_filter_fix
Open

Fix range filter bug on paging, don't sort on values#67
lbrant1 wants to merge 3 commits into
imsweb:masterfrom
lbrant1:range_filter_fix

Conversation

@lbrant1

@lbrant1 lbrant1 commented Oct 16, 2018

Copy link
Copy Markdown
Contributor

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
Comment thread seeker/views.py Outdated
values = sorted(values)
parts.extend(urlencode({key: val}) for val in values)
return '&'.join(parts)
pass

Copy link
Copy Markdown
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?

Comment thread seeker/views.py Outdated
if ignore and key in ignore:
continue
if not data[key]:
if not data.getlist(key) or not any(data.getlist(key)):

Copy link
Copy Markdown
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
Copy Markdown
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