-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Fixes #11652] Facets: wrong count on multiple tkeywords filtering #11655
Merged
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
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #11655 +/- ##
=======================================
Coverage 62.90% 62.90%
=======================================
Files 875 875
Lines 52536 52543 +7
Branches 6604 6604
=======================================
+ Hits 33047 33052 +5
- Misses 17966 17969 +3
+ Partials 1523 1522 -1 |
etj
force-pushed
the
11652-facets-bad-count
branch
from
November 3, 2023 15:46
12ddf77
to
cb9a663
Compare
giohappy
approved these changes
Nov 6, 2023
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-4.2.x 4.2.x
# Navigate to the new working tree
cd .worktrees/backport-4.2.x
# Create a new branch
git switch --create backport-11655-to-4.2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 c937f5e42ead119bdfcd709a4ea23d3db37f5e7b
# Push it to GitHub
git push --set-upstream origin backport-11655-to-4.2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-4.2.x Then, create a pull request where the |
giohappy
pushed a commit
that referenced
this pull request
Nov 6, 2023
…11655) * [Fixes #11652] Facets: wrong count on multiple tkeywords filtering - tkeywords * [Fixes #11652] Facets: wrong count on multiple tkeywords filtering - category * [Fixes #11652] Facets: wrong count on multiple tkeywords filtering - region * [Fixes #11652] Facets: wrong count on multiple tkeywords filtering - keywords
giohappy
added a commit
that referenced
this pull request
Nov 6, 2023
* thesaurus topics should only return its own keys (#11644) * [Fixes #11652] Facets: wrong count on multiple tkeywords filtering (#11655) * [Fixes #11652] Facets: wrong count on multiple tkeywords filtering - tkeywords * [Fixes #11652] Facets: wrong count on multiple tkeywords filtering - category * [Fixes #11652] Facets: wrong count on multiple tkeywords filtering - region * [Fixes #11652] Facets: wrong count on multiple tkeywords filtering - keywords --------- Co-authored-by: Emanuele Tajariol <etj@geo-solutions.it>
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.
The query has been completely rewritten.
Checklist
For all pull requests:
The following are required only for core and extension modules (they are welcomed, but not required, for contrib modules):
Submitting the PR does not require you to check all items, but by the time it gets merged, they should be either satisfied or inapplicable.