Fix: Next Queries not being calculated when using Related Tags #1428
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.
Pull request template
Describe the purpose of the change, the specific changes done in detail, and the issue you have fixed.
Make Next Queries requests take into account when a query is selected along with a related tag:
storeModule
have a RTs array in the state to save the selected RTsstoreModule
have a mutation to update the RTs in the statestoreModule
have a query getter to concat the query with the RTs (if selected)request
use the query getter.SelectedRelatedTagsChanged
& callsetRelatedTags
mutationMotivation and context
Currently, the Next Queries module doesn’t take into account the selected related tags. This creates some weird scenarios like having NQ when searching for novela negra but not having NQ when searching for
novela
and then selecting the RTnegra
Type of change
What is the destination branch of this PR?
Main
How has this been tested?
Test in CDL:
Use a local build of x-components &
env=live
to test?env=live&query=novela%20negra
?env=live&query=novela
+ select the “negra” RTThen:
Tests performed according to testing guidelines:
Checklist: