Closed hadley closed 3 years ago
"a" is indeed matching (since the pattern is "war"). One way to omit single character matches is to set minMatchCharLength
to a value > 1.
In that case, this is probably a duplicate of #504, because it surprises me that the match can be shorter than the search term.
Thinking about this more, I think I generally want a prefix match — i.e. if the use has typed "war", I want to match "war", "warfare", "warlord", but not "award", and not "a". This isn't quite ^war
because I'd still like some fuzziness , and I want to apply it automatically to searches (although I guess I could just turn on extended search and paste "^" to the front of the search string).
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days
Describe the bug
On the live demo page, I use the following code:
and it returns two results:
The matches appear to include text that doesn't match. E.g. the first match includes indices
[1, 1]
, i.e. "a".Version
6.4.2