You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When searching for an exact match using single-quote before the search string, with extended search mode enabled:
I would expect the result to be exact as, non-fuzzy and case-sensitive. But the matches are only non-fuzzy.
For example: const fzf = new Fzf(['Hello', 'hello', 'HeLLo'], {match: extendedMatch}); const result = fzf.find("'hello").map(({item}) => item); // result: ['Hello', 'hello', 'heLLo']
But I would expect: const result = fzf.find("'hello").map(({item}) => item); // result: ['hello']
My proposal is the same as in the ticket mentioned above, either make a another function for a true exact-match and rename the current one to non-fuzzy match, or make the current exact-match case-sensitive.
The text was updated successfully, but these errors were encountered:
This library closely follows the core logic of fzf-cli. And to avoid the risk of breaking backwards compatibility, I'll wait for fzf-cli to get an implementation first. I have subscribed to the ticket you mentioned, and rest assured, this library would get an update as well.
When searching for an exact match using single-quote before the search string, with extended search mode enabled:
I would expect the result to be exact as, non-fuzzy and case-sensitive. But the matches are only non-fuzzy.
For example:
const fzf = new Fzf(['Hello', 'hello', 'HeLLo'], {match: extendedMatch});
const result = fzf.find("'hello").map(({item}) => item); // result: ['Hello', 'hello', 'heLLo']
But I would expect:
const result = fzf.find("'hello").map(({item}) => item); // result: ['hello']
There is a similar request for the fzf-cli: junegunn/fzf#2613
My proposal is the same as in the ticket mentioned above, either make a another function for a true exact-match and rename the current one to non-fuzzy match, or make the current exact-match case-sensitive.
The text was updated successfully, but these errors were encountered: