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

Make addFilter generic so we can contribute upstream #202

Closed
Tracked by #63
avaleske opened this issue Jul 16, 2021 · 0 comments · Fixed by #257
Closed
Tracked by #63

Make addFilter generic so we can contribute upstream #202

avaleske opened this issue Jul 16, 2021 · 0 comments · Fixed by #257
Assignees
Labels
epic: filtering Tickets related to Filtering size: 3 About a day of work
Milestone

Comments

@avaleske
Copy link

avaleske commented Jul 16, 2021

Per Sean's comments on addFilter() here we should make addFilter() generic.

If we refactor out the listings specific map so that it's provided by the caller, then other entities can use this filter logic too.

Once we do this, we can contribute filters upstream (#192)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic: filtering Tickets related to Filtering size: 3 About a day of work
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant