-
Notifications
You must be signed in to change notification settings - Fork 316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce native facet mappings #2071
Merged
brandwaffle
merged 9 commits into
10up:develop
from
moraleida:feature/introduce_facet_mappings
Apr 30, 2021
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
09f9258
introduce new mappings for term facets
92db192
remove debug statement
32eb2e5
let ES handle json as string
d3da4a0
Revert "let ES handle json as string"
84fc076
port facet mapping to all versions
6294869
introduce filter ep_facet_use_field to allow selecting which field to…
4dd4a42
introduce term_taxonomy_id for parent terms
e4707a6
Merge branch 'develop' into feature/introduce_facet_mappings
Rahmon f094084
Add @since to the filter ep_facet_use_field
Rahmon File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@felipeelia Can you check if there a reason why we only collect the
term_taxonomy_id
here and not when getting parent terms in line 462 below? I have checked annotations and this difference has been around since tt_ids were introduced in #840I've now bumped into an issue in hierarchical taxonomies in which the new native facet is stored twice because of this. It's stored once with
term_taxonomy_id
(created here) and once without it (created inget_parent_terms()
below, whenever a child term is stored).Adding
term_taxonomy_id
to parent terms fixes the issue, but I wanted to check if there is any reason why it didn't have that in the first place.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it was just something we missed until now, @moraleida.
@brandwaffle can we aim to have this merged in 3.6.0?