Add asciifolding filter to keyword_normalizer for consistent accent-insensitive search #277
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.
Addresses review feedback on #276 to ensure accent-insensitive search behavior applies consistently across both analyzed text fields and keyword fields.
Changes
asciifoldingfilter tokeyword_normalizerin ElasticSearch configurationPreviously,
asciifoldingwas only applied tomy_analyzer(used for text fields like title/description). Keyword fields (tags, autoTags, textTags) usedkeyword_normalizerwithoutasciifolding, creating inconsistent search behavior where searching for "Vezelay" would match text content containing "Vézelay" but not tags containing "Vézelay".✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.