Add support for defining lunr similarity tuning parameters and custom search boost factors #67
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
- Add support for defining similarity tuning parameters b, and k1 - Add support for defining boost factors for content and titles
|
Thank you @JulesBlm, and sorry for the delay! |
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.
Hi, thanks for this great package. I needed to tweak the lunr similarity tuning parameters and boosts slightly to improve the search results. This PR add supports for defining these (parameters
bandk1) and boost factors for title and content matches in thelunrfield in the config options. The defaults are the same as they used to be:b = 0.75,k1 = 1.2,titleBoost = 5, andcontentBoost = 1.All tests pass and some testing with my docs showed that my search results got better.