Fix Docs search improvement: Improve fuzzy search#3106
Conversation
In the app environment, the prompt input was initialized using `options.value`, so `defaultValue` was not reflected. This change ensures that `defaultValue` is used when provided, while keeping backward compatibility with `options.value`.
0b52df1 to
4a5b06e
Compare
|
letting you know that i'm still looking at this, please give me some time to review it |
|
hi @angelinazzz1809 , the PR seems to contain some merge conflict in |
|
Thanks! The other account (yiqingzhao1216) is also mine — I accidentally used a different local git commit identity while pushing from my local environment, which caused the CLA mismatch. I've signed the CLA for that account as well, so it should be fully resolved now. And I synced with the latest upstream changes and resolved the merge conflict in gui/src/UI. The PR has been updated, so it should run correctly now. Please let me know if there are still any issues. Appreciate you taking the time to review this! |
Fixes #2362
Summary
This PR improves the docs search experience by integrating Fuse.js fuzzy search and refining search result behavior.
Changes made
Current behavior
Notes
There are still some limitations with long-word typo matching (for example certain missing-character cases), especially when indexing large page content blocks.
I also started moving toward section-level indexing as suggested in the issue discussion(related to #2599), which should further improve fuzzy matching quality and relevance ranking.
Feedback is very welcome!