fix(ui) Fix filtering logic for everwhere generating OR filters #9116
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.
Wherever we submit orFilters, we're using
generateOrFilters
which converts out nested filters into the correct format. Unfortunately we were only separating out these nested filters in one function above this one for the main search page (the only place we have nested filters). However we also use this function without using the main function above this to filter out nested vs non-nested filters forscrollAcrossEntities
- which means we were getting errors in the incorrect format.Checklist