-
Notifications
You must be signed in to change notification settings - Fork 15
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
Allow getCatalog wanda call to filter by provider #1098
Allow getCatalog wanda call to filter by provider #1098
Conversation
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.
Overall a good job, I made some suggestions so that we end basically collecting an env
object that we end up passing to the request. I'm uncertain about the suggestion I made on assets/js/state/actions/catalog.js
because actually having a RORO there would ensure some extra parsing.
Ref about RORO: https://www.freecodecamp.org/news/elegant-patterns-in-modern-javascript-roro-be01e7669cbd/
0c1ac6c
to
c350f26
Compare
c350f26
to
a188b39
Compare
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
Description
This PR adds a
provider
search param to wanda's getCatalog call. This is particularly useful in the checks selection view, as we might want to limit the display of checks that can't be applied to certain provider.How was this tested?
Manually by running wanda and checking that the checks selection view causes the search param to be added to the request while the catalog view doesn't.