Score is not working correctly

Hi,

in last version 3.6.1 the score is not between 0 and 1. This can be check on https://fusejs.io/ too.

Example request + config:

  shouldSort: true,
  includeScore: true,
  threshold: 0,
  location: 0,
  distance: 0,
  maxPatternLength: 32,
  minMatchCharLength: 1,
  keys: [
    "title",
    "author.firstName"
  ]
};
var fuse = new Fuse(list, options); // "list" is the item array
var result = fuse.search("Old Man's War");

the output:

[
  {
    "item": {
      "title": "Old Man's War",
      "author": {
        "firstName": "John",
        "lastName": "Scalzi"
      }
    },
    "score": 2.220446049250313e-16
  }
]

[acnebs]

Yeah, this broke my logic and took me a while to debug. The docs should definitely be changed if an exact match is no longer strict equality 0.

@MadsMadsDk I’m not sure that is the best way to do it, as partial match scores can be as low as 0.001, which with your fix would be cast as “perfect” even though it’s not quite.

I’ve gone with this for the time being:

const perfectMatch = result.score < 1E-10;

But I think it would be very good to have a solution with a strong guarantee when a result is a perfect match.

[krisk]

Addressed this in v5.2.2-alpha.0.

However, I’m undecided about this. I’ve started a discussion in #397.

[Will close this and use the above issue instead]