Should-be perfect match has non-zero score

Describe the bug

When searching for a keyword in a list of objects, the search works and finds matches. However, the should-be perfect matches return a non-zero score like 2.220446049250313e-16. This should be 0 as it is a perfect match, but due to not being exactly 0, it continues the search.

The Minimal Production below gives this as its result:

0: {item: {…}, refIndex: 0, matches: Array(1), score: 2.220446049250313e-16}
1: {item: {…}, refIndex: 1, matches: Array(1), score: 0.2}
2: {item: {…}, refIndex: 2, matches: Array(1), score: 0.2}
3: {item: {…}, refIndex: 3, matches: Array(1), score: 0.2}
4: {item: {…}, refIndex: 4, matches: Array(1), score: 0.2}

Version

6.4.1

Is this a regression?

Yes, the previous version in which this bug was not present was: 3.6.1 (Im using it in another project, there it works fine)

🔬Minimal Reproduction

  const items = [
    {
      value : 'test1',
    },
    {
      value : 'test2',
    },
    {
      value : 'test3',
    },
    {
      value : 'test4',
    },
    {
      value : 'test5',
    },
  ];

  const fuse = new Fuse(items, {
    ignoreLocation : true,
    includeMatches : true,
    includeScore   : true,
    keys           : ['value'],
  });

  console.log(fuse.search('test1'));

[Emroni]

fuse.search('test2').forEach((it) => it.score = Number(it.score.toFixed(2)));

I’ve used that workaround too, although I would recommend using Math.round((score * 100) / 100) as its much slower to use toFixed() and then casting to `Number. Especially if there are thousands of records, it would slow it down significantly.

[smasala]

Bump