fix: add tokenizer for the query string #3
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.
Problem: lunr query search term depends on spaces for each token. However, lunr.ja plugin tokenize the fields (documents) using japanese segmenter.
So, for example the resulting token created for the field 標準製品仕様は will be 標準, 製品, 仕様, and は (as demonstraded in http://chasen.org/~taku/software/TinySegmenter/)
Solution: To search for 標準製品 (which is two words), tokenize the input query using the same tokenizer. Then convert it back into lunr query search term.
Limitation: since this method essentially add spaces to Japanese words (as dictated by the segmenter used by lunr.ja). Using wildcards, fuzzy, boosts (https://lunrjs.com/guides/searching.html) in search method would produce false result.