[RFC] Separate fuzziness score from sort score

[This is in response to #354]

Currently, the score that is exposed in search results is calculated as a function of the following:

• Internally calculated fuzziness score
• User inputted weight of the key
• Field-length norm (i.e, the shorter the field, the higher the weight)

Using the above, we compute the final score, which is what is used to sort the list.

As a result, exact matches are not necessarily given a final score of 0. As noted in #354, however, people may want to use the score to decide whether a match was indeed exact.

To address this, in v5.2.2-alpha.0 I thus separated the “sort score” ($score) from the “fuzziness score” (score), of which only the latter is exposed.

I am undecided on whether I will publish this as “latest”. I would love some feedback.

[danielfdickinson]

I will try and look at this implementation soon-ish (heavy on the ‘ish’ probably), but I think keeping the sort score separate from fuzziness is a really good idea.

[github-actions[bot]]

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