You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
Current behavior:
Two commands with nearly identical display names that matches the query well can have significantly different scores. If one of them features both a tag and a description that contains the query, it will have maybe 2-3x higher score, maybe even being surpassed by other commands that also have descriptions and tags.
Expected behavior:
Two commands with nearly identical display names that matches the query well should have a very similar score. If the query matches descriptions or tags better than display name, that score should be used instead.
Potential fix:
For each item, use the maximum score out of the three:
Here is the relevant code snippet for sorting.
Current behavior:
Two commands with nearly identical display names that matches the query well can have significantly different scores. If one of them features both a tag and a description that contains the query, it will have maybe 2-3x higher score, maybe even being surpassed by other commands that also have descriptions and tags.
Expected behavior:
Two commands with nearly identical display names that matches the query well should have a very similar score. If the query matches descriptions or tags better than display name, that score should be used instead.
Potential fix:
For each item, use the maximum score out of the three:
itemScore = Math.max(displayNameScore, tagScore, descriptionScore)
The text was updated successfully, but these errors were encountered: