Used Japanese tokenization in queries for accurate word searching in … #2
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.
Overview
This PR addresses the issue where searching for compound Japanese terms like "標準製品" did not return the expected matches in Lunr.js. The solution involves:
Japanese Morphological Segmentation: Utilizes the
lunr.ja
plugin to ensure consistent tokenization of Japanese text during both indexing and querying.Wildcard Query Enhancement: Appends trailing wildcards (
*
) to each token in the search query to enable partial and prefix matching.Error Handling: Ensures that queries are constructed using Lunr's query builder API to prevent parsing errors and maintain consistency.
Changes Made
lunr.ja
plugin for accurate Japanese tokenization.Search
component to tokenize queries using the same pipeline.