Filter search results before showing to exclude selected items. #171
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 of the Change
As described in #159, currently, we can pick duplicate content using
ContentPicker
. We already have a logic in place to exclude selected items atContentPicker
component. But this is happening because of the seachQuery cache in theContentSearch
component, the results for search keywords get stored in Object and whenever the same keyword is entered, it shows the stored results without filtering the results byexcludeItems
.This PR contains a minor change for applying
filterResults()
on search results before showing it to prevent showing duplicated items.Closes #159
How to test the Change
npm i && npm run build
npm i && npm run build && npm run wp-env start
Changelog Entry
Credits
Props @Firestorm980 @iamdharmesh
Checklist: