Exact match result is not the first item returned

[alex-galey]

Do you want to request a feature, an issue, or report a bug?
Issue

What is the current behaviour?
Exact match result is not the first item returned

If the current behaviour is a bug, please provide the steps to reproduce.
This is the returned array for the query=lille with City.fuzzySearch(query).limit(5).exec() :

[
  { "nom": "Lillers",      "confidenceScore": 4.300000000000001 },
  { "nom": "Lillemer",     "confidenceScore": 4.300000000000001 },
  { "nom": "Lille",        "confidenceScore": 4.300000000000001 },
  { "nom": "Lillebonne",   "confidenceScore": 4.300000000000001 },
  { "nom": "Ille-sur-Têt", "confidenceScore": 4.2               }
]

What is the expected behaviour?
Exact match "Lille" should have a higher confidenceScore than the others

I'm using this function to bring the exact match up :

for (let i=0; i<answer.length; i++) {
    if (answer[i].nom.toLowerCase() === query) {
        answer.unshift(answer[i]);
        answer.splice(i+1,1);
    }
}

If this is a feature request, what is the motivation or use case for changing
the behaviour?

Please mention other relevant information such as Node.js and mongoose version.
node v14.4.0
mongoose 5.11.15

[coolb0y]

You can solve this issue by sorting this array by metascore that is confidence score the top results(all having highest confidance score) by length in increating order so "Lille" will always come first . I think even if they are not sorting result I think "Lille" should still be higher than other result with same score as gramitically "Lille" will appear higher in database than other words .

[alex-galey]

What I meant is confidenceScore should be influenced by the "exact matching" factor.

Don't you / doesn't anyone think it should ?

(I didn't try this again recently)