fix: re-initialize filter repository on namespace change #3668
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.
Changes
We addressed an issue that occurred while navigating through various HCMS entry lists.
The issue was caused by the
FilterRepository
not being re-initialized upon a change innamespace
.To fix this, we implemented a check to determine if any new
namespace
orclient
was received and useduseMemo
to memoize the returned value.How Has This Been Tested?
Jest