[jk] Fix filters from being reset when items fetched #4859
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
/pipeline-runs
and/pipelines/[pipeline_uuid]/triggers
were being reset unexpectedly due to the filter component getting re-rendered with stale data every time a certain resource was being fetched. This PR fixes this issue.How Has This Been Tested?
Before (filters periodically reset):
After (filter state persists):
Checklist
docs/mint.json
cc: