There are a few known bugs when using GlFilteredSearch (the component we will rely on).
This component looks to be in use already by the Monitor team. So can product confirm here if we will push forward introducing pipeline filters with these known bugs? @kencjohnston@thaoyeager
Filter with Trigger Author, ensure table updates correctly with correct pipelines by author
Filter with Branch Name, ensure table updates correctly with correct pipelines by branch name
Filter with multiple filters (i.e. both branch name and author)
Ensure query params are correct when making api call
Ensure invalid/illegal inputs are being captured/handled appropriately
Removing filters will update table data (is this a deliverable for this issue?)
How do we ensure data integrity from API result? I.e we only get list of authors from the right group of people, and only branches in the right project. (This is an existing functionality we are just bring over from some where? Or is this a new functionality?)
Removing filters will update table data (is this a deliverable for this issue?)
I just pushed up a bit of code on my WIP MR. When filters are cleared and then an empty search is invoked, the API query params are updated. So we can write testing around removing filters and then submitting to see results.
How do we ensure data integrity from API result? I.e we only get list of authors from the right group of people, and only branches in the right project. (This is an existing functionality we are just bring over from some where? Or is this a new functionality?)