ZQ Fuzzy Search need a small update

vlebert · March 16, 2022, 12:45pm

Hi

Thanks for the plugin ZQ Fuzzy Search.

However, I would advise a little update
Currently, the tokenize options is not working. In fact tokenize in not supported by Fuse.js anymore

github.com

krisk/Fuse/blob/master/CHANGELOG.md#version-400-beta

# Changelog

All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.

### [6.5.3](https://github.com/krisk/Fuse/compare/v6.5.2...v6.5.3) (2021-12-23)


### Bug Fixes

* **logical:** scoring for logical OR ([6f6af51](https://github.com/krisk/Fuse/commit/6f6af51cc39058fafea6b126f7120afc4f7c192a)), closes [#593](https://github.com/krisk/Fuse/issues/593)

### [6.5.2](https://github.com/krisk/Fuse/compare/v6.5.1...v6.5.2) (2021-12-23)

### [6.5.1](https://github.com/krisk/Fuse/compare/v6.5.0...v6.5.1) (2021-12-23)


### Bug Fixes

* rollback min node version ([9918f67](https://github.com/krisk/Fuse/commit/9918f67ba9b6b9b54e53576312fa33a51f428a9d))

This file has been truncated. show original

Could you update the plugin and implement the extended searching option?

github.com/krisk/Fuse

[RFC] Extended searching in v4.0.0-beta

opened 12:13AM - 10 Mar 20 UTC

closed 02:54AM - 16 Mar 20 UTC

krisk

discussion

I recently added [extended search](https://github.com/krisk/Fuse/tree/extended-s…earch/src/extended-search) (inspired by [fzf](https://github.com/junegunn/fzf/blob/master/README.md#search-syntax)). I'd love our thoughts 🙏 ### Why? This form of advanced searching allows the user to fine-tune their results. It can be used to immediately exclude a large part of their search body before doing the final fuzzy matching. It's reminiscent of Unix-like terminal commands. ### Search syntax Fuse.js will work exactly as before, and if you give the option `useExtendedSearch:true`, you can use the following syntax in the search query: | Token | Match type | Description | | ----------- | -------------------------- | -------------------------------------- | | `jscript` | fuzzy-match | Items that match `jscript` | | `'python` | exact-match | Items that include `python` | | `!ruby` | inverse-exact-match | Items that do not include `ruby` | | `^java` | prefix-exact-match | Items that start with `java` | | `!^earlang` | inverse-prefix-exact-match | Items that do not start with `earlang` | | `.js$` | suffix-exact-match | Items that end with `.js` | | `!.go$` | inverse-suffix-exact-match | Items that do not end with `.go` | White space acts as an **AND** operator, while a single pipe (`|`) character acts as an **OR** operator. For example, this search query: ```bash "^core go$ | js$ | py$ xy$" ``` is interpreted as the following logical expression: ```bash ("^core" AND "go$") OR "js$" OR ("py$" AND "xy$") ``` ### Usage ```js const options = { // Enable extended search useExtendedSearch: true, keys: [ /*...*/ ], } const fuse = new Fuse(/*...*/) fuse.search('^jscript .python$ | ruby | !java') ``` --- **Do we still need the previous implementation of tokenization (i.e, see #355)?** With extended search, we have more useful form of fuzzy tokenization, where you could provide a pipe-delimited search query: ```js fuse.search("jcript | pthon | rby") ``` ### Feedback? Questions? Please have a go at it 😄

Thanks for your work
Valérian LEBERT

Ecaterina · March 17, 2022, 12:37pm

Hello, @vlebert
Thanks for reaching out and for your involvement.

Seems like the tokenized is really excluded, however, it is not influenced the plugin functionality.

We will check the provided documentation and will discuss with our developer possible plugin improvement.
Thanks a lot for this information.

Best regards,

Ecaterina · March 22, 2022, 12:00pm

Hello, @vlebert

By this message, I would like to notify you that we removed all the files, that were deprecated by the library author, i.e. Tokenize and Match all Tokens.

Please upgrade the plugin to the latest version (1.10.0) and use it within your application

Best regards,

vlebert · March 22, 2022, 4:31pm

Hi

Thanks for your reply
I did update but this options still appears on my side

Am I doing something wrong ? Moreover could you add the useExtendedSearch option (boolean).
It is now the proper way of doing tokenized searches

Ecaterina · March 24, 2022, 8:19am

Hello, @vlebert
Sorry for this inconvenience.

Please note that in order to find an updated plugin element you should not only upgrade the plugin but remove it from your page.
So, you need to:

Remove plugin element from your page;
Upgrade the plugin (or check if you are using the latest version);
Place the plugin element on your page once again.

Now, the plugin element is looking like this:

Please try it and let me know about the result.
Best regards,

vlebert · April 1, 2022, 11:46am

Hi

I do have the expected result now, thanks.

Just missing the useExtendedSearch option (just a small boolean parameter to add) whiech would allow to do tokenized queries with syntax in the query string

Regards

Ecaterina · April 4, 2022, 1:12pm

Hello, @vlebert

Thanks for your suggestion!
We’ve taken into consideration the possibility to add such a feature for future plugin updates. We need to see how feasible it will be accordingly to our current plans

Thank you!Best regards,