Fuzzy search results aren't displayed in popularity order

[peterbe]

Go to the search widget and paste in /foreach. That should match every document that has the word foreach in the URI.

We know from Elasticsearch that searching for foreach
displays them in roughly this order:

1. Array.prototype.forEach()
2. Map.prototype.forEach()
3. Set.prototype.forEach()
4. TypedArray.prototype.forEach()
5. etc.

they all contain the word foreach in the title so all you have left to rank is the popularity. But it's clearly not working:

[peterbe]

This is kinda the explanation. When passed in throug the import { match } from "fuzzyjs"; function from fuzzyjs module, it produces those score values that are negative.

I printed them out to try to understand how it filters things:

Why does /en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/forEach get a score of -32?!
It has to do with the fact that it's long.

I also see lots of new options in the latest version of https://www.npmjs.com/package/fuzzyjs but I don't think we're using that version.

[peterbe]

If you remove the filtering my score > 0 this happens:

[tannerdolby]

Why does /en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/forEach get a score of -32?! It has to do with the fact that it's long.

Hmm that is quite odd that the score would be negative. But it seems that from the console log output you provided that indeed, the longer the search result the more negative its score is.

And when you remove the filtering score so that they must be > 0 we definitely get some search results that don't make much sense. Now that I've read the conversation in #28 within fzf-for-js, I better understand why we would want a boolean sort property so like mentioned in the corresponding PR, we can better control how the sorting happens to have

Output: lisp, kotlin, elixir

become this with the sorted boolean set to false so we would have the natural sorting that appears in the list array option:

Output: kotlin, elixir, lisp