Issue to track v5.0.0 beta feedback

This issue is for collecting feedback and possible issues during the beta testing of MiniSearch v5.0.0, which includes an improved scoring algorithm.

[lucaong]

Decision about the issue above was to keep the weights unchanged, the relevant discussion is in #146

[lucaong]

Here is one case that might need tweaking before releasing v5.0.0: when using both prefix and fuzzy match, if a term matches one document with prefix search and another with fuzzy search, all else being equal (including the edit distance, field length, etc.) by default the prefix match should probably score slightly higher than the fuzzy match, because it tends to be more relevant.

Here is a spec reproducing the issue:

it('ranks prefix matches higher than fuzzy matches with the same distance, all else being equal', () => {
  const ms = new MiniSearch({ fields: ['text'] })
  const documents = [
    { id: 1, text: 'unicorns' },
    { id: 2, text: 'unikorn' }
  ]
  ms.addAll(documents)
  expect(ms.documentCount).toEqual(documents.length)

  const results = ms.search('unicorn', { fuzzy: 0.2, prefix: true })
  expect(results.map(({ id }) => id)).toEqual([1, 2])
})

Also, this is mentioned by at least one user in this issue report (see the comment about order of results in the first message).

/cc @rolftimmermans