Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Thank you for your library #46

Open
NistorCristian opened this issue Sep 18, 2018 · 3 comments
Open

Thank you for your library #46

NistorCristian opened this issue Sep 18, 2018 · 3 comments

Comments

@NistorCristian
Copy link

Hi,

This is not an issue. I just want to thank you @farzher for your amazing library. I just released a search library for Ghost Blogging Platform called ghost-search and it's using fuzzysort as a search algorithm.

After a testing multiple libraries like lunr, fuse, and other search libraries, fuzzysort seems to be the one that does the job properly. When I started I was not expecting that finding a search library would be so hard. Boy I was wrong.

Thank you again and keep up the good work.

@d3lm
Copy link

d3lm commented Oct 29, 2018

Totally agreed! I have also tested a bunch of other libraries and this really does its job really well. Thanks for your work on this.

@WalterGR
Copy link

WalterGR commented Jun 1, 2022

I agree. I've been hacking on a local copy of https://github.com/minhanhhere/chrome-faster-bookmark (not my project; screenshots here: https://chrome.google.com/webstore/detail/faster-bookmark-add-bookm/fibadljlplamppipiebabkdehecpabce) which uses Fuse. I'm getting much better results with your library. Thanks so much!

@dbuezas
Copy link

dbuezas commented Oct 5, 2024

Plus one, I switched from fuse.js to fuzzysort in command palette extension for chrome (https://github.com/dbuezas/chrome-palette) and the search results are a lot more intuitive 🎉

The only thing that is less good is that it is less of a stable search, meaning that the ordering of the input has less impact on the output.

In the extension I pre-sort commands by last used, and if the last one I used was Split horizontally, searching for Split still puts Split vertically first.

I assume the scoring function scores the latter higher because the match represents a higher percentage of the characters.

Anyway, great lib!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants