Don't sort extension search alphabetically #5649
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sorting the extensions alphabetically gives more visibility to packages early in the alphabet. Instead, retain the sort order from the registry, which is based on a composite score including: - How well the package matches the search text. - A package "score": https://docs.npmjs.com/searching-for-and-choosing-packages-to-download#package-search-rank-criteria
|
Alternatively, this can instead only sort the |
|
+1 to keeping the registry score for now, if that seems good. |
|
Thanks! |
lock
bot
added
the
status:resolved-locked
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sorting the extensions alphabetically will artificially give more visibility to packages early in the alphabet. Instead, retain the sort order from the registry, which is based on a composite score including: