This repository has been archived by the owner on Apr 4, 2023. It is now read-only.
Release v0.26.4: returns facets even when there is no value associated to it + bug fix during indexation + bug fix on typo-tolerance #519
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
Don't merge it until we take a decision if this should be fixed or not: meilisearch/meilisearch#2358 |
curquiza
changed the title
Release v0.26.4: returns facets even when there is no value associated to it
Release v0.26.4: returns facets even when there is no value associated to it + bug fix during indexation
May 3, 2022
bors try |
ManyTheFish
approved these changes
May 3, 2022
bors merge |
bors bot
added a commit
that referenced
this pull request
May 3, 2022
519: Release v0.26.4: returns facets even when there is no value associated to it + bug fix during indexation r=curquiza a=curquiza I cherry-picked the commits from these PRs - #518 - #522 `release-v0.26.4` has been started from the tag `v0.26.3` and not from main The release tag `v0.26.4` will be done on the branch `release-v0.26.4` once this PR is merge Co-authored-by: Kerollmops <clement@meilisearch.com> Co-authored-by: Clémentine Urquizar <clementine@meilisearch.com>
bors merge- |
Canceled. |
Still missing #520 to be put into this PR, sorry |
curquiza
changed the title
Release v0.26.4: returns facets even when there is no value associated to it + bug fix during indexation
Release v0.26.4: returns facets even when there is no value associated to it + bug fix during indexation + bug fix on typo-tolerance
May 3, 2022
bors try |
Kerollmops
approved these changes
May 3, 2022
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.
bors merge
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I cherry-picked the commits from these PRs
release-v0.26.4
has been started from the tagv0.26.3
and not from mainThe release tag
v0.26.4
will be done on the branchrelease-v0.26.4
once this PR is merge