Implemented ability to add localizations of selected terms to filter #8730
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When there are several localisations for terms, it's currently required to select all of them in the filter for projections/queries.
This becomes troublesome to keep track of as more languages are added, and the localisations of terms are added to the tenant. This is especially an issue when accounting for the fact that the different permissions required (e.g. to handle localizing content, taxonomies and configuring queries) may be spread to different users.
In this PR, we tackle this by adding an option to the
TermsFilterthat would allow automatically localizing the selected terms (i.e. including their localized versions in the query).