Reset table offset when DagFiltering changes #51694
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.
Remove the
offsetfrom the search param when we modify DagFilters.Otherwise this would wrongly display "no result found" on the front-end but just because we are requesting an offset that does not exist.
How to reproduce:
DagsFilterscomponent, see that 'no results' will appear (suposing there isn't 2 or 3 pages of result for that filtered query), but actually there are some results.Before
(clicking on "failed" when on page 3 will not reset the offset to 0, API will resturn no result for page 3 + failed state ending up in no result displayed in the UI).

After
(clicking on "failed" when on page 3 will reset the offset to 0 and display the proper result)
