Closed jeancroy closed 7 years ago
Ok the problem is a bit complicated because there's code in place to use the proper matcher.
However I can replicate
v1.15
v1.17 (1.18beta looks the same)
Both have alternate scoring turned on. Maybe something broke the propagation of settings in 1.17 ?
Looks like a regression with the jQuery removal then. Thanks for catching this.
/cc @as-cii
Since about atom 1.1, the alternate scoring option is provided that decide both how to rank and highlight the result.
On current version, alternate scoring option only decide ranking, and it seems highlight is always rendered using classic fuzzaldrin. I think it's important to have both together as I consider highlight an explanation of current ranking.
It's very probable the behavior broke when switching the underlying component to remove jquery. It's hard to detect because there's no test for it and one must be in knowledge of the algorithms to spot the differences.
Here's a recent example, typical of classic fuzzaldrin.
One can see that the word
member
is split because classic fuzzaldrin select first occurence ofm
then first occurence ofe
following that m then firstm
thenber
Here's a reference highlight with fuzz-aldrin-plus outside of atom. One can see that the algorithm try to group matches together instead of processing greedy left to right.
Now that algorithm isn't perfect and here we have an issue with
-payment
being before plain edit. But the overall highlight seems more intuitive.The reason I write this is that 'scattered letters' was by far the main complains with classic fuzzaldrin and complains stated to reappears.