-
Notifications
You must be signed in to change notification settings - Fork 5
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
Update Search page to manage profile filters #777
Comments
8 tasks
This was referenced Mar 3, 2023
pjmonks
added a commit
that referenced
this issue
Mar 9, 2023
- New child component for CatalogueSearchComponent - Track state of all profile filters using Angular FormArray - Use profile providers and definitions to guide user for which namespaces and keys to use for filters - Clean up code in CatalogueSearchAdvancedForm - Move "More filters" button to parent component - Section on CatalogueSearch page now controls visibility of the advanced form and profile filter list - Update code and tests to have @ViewChild mapping work - Update parent/child communication to handle resets and track validity - Add and update tests
pjmonks
added a commit
that referenced
this issue
Mar 9, 2023
abwilson23
added a commit
that referenced
this issue
Mar 14, 2023
pjmonks
added a commit
that referenced
this issue
Mar 14, 2023
gh-777 Add profile search filter selection to Search page
github-project-automation
bot
moved this from Open PR
to Merged to Develop / Waiting to release
in MDM State
Mar 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The Search page needs to support advanced filter controls to select one or more profile filters to be used as search criteria when searching the catalogue.
A profile filter is a combination of:
Design
Features
The "Advanced" section of the search page should include a set of controls, similar to above, to add, edit and remove profile filters.
Adding a profile filter may need to have a limit imposed, depending on if the UI ends up being too cluttered e.g. a maximum of 3, or 5, profile filters.
Each row should provide:
GET /api/profiles/providers
endpointFor entering an input value, two options will currently be supported:
Out of scope
This task should only focus on the UI. Submitting the profile filters to the Search Listing page will be handled in task #779.
The text was updated successfully, but these errors were encountered: