-
Notifications
You must be signed in to change notification settings - Fork 2
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
WEBDEV-5583 Add filters
param to handle facet/date-range constraints
#23
Conversation
Codecov Report
@@ Coverage Diff @@
## main #23 +/- ##
==========================================
+ Coverage 82.05% 85.15% +3.10%
==========================================
Files 24 26 +2
Lines 1989 2405 +416
Branches 106 108 +2
==========================================
+ Hits 1632 2048 +416
Misses 345 345
Partials 12 12
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! I especially appreciated the way that filter-map-builder-test.ts
shows how to use the class
The PPS accepts a
filter_map
URL parameter that specifies constraints on metadata field values, such as including/excluding certain values or ensuring they are within a given numeric range. This PR adds afilters
param and related types to the search service so that it can accept and pass along these constraints. This will allow constraints like selected/negative facets and date picker queries to be more cleanly passed to the PPS (rather than the current approach of joining them into the query string itself).This PR also includes several updates to the demo app, both to enable testing multiple filters and to improve readabililty/folding.