New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow control of Sorting in Package Manager UI Browse tab #2585
Comments
Currently the Package Manager UI shows a list of packages that is inline with the sorting order on NuGet.org search results based on 'popularity'. However, users need varied ways to search to get to the right package quickly. E.g
|
Just to rephrase our default search is not just popularity, rather it's overall relevance of the package where popularity is a major contributor but not the only contributor. Relevance also includes other items like, how many times that search term exists across package fields like description, or tags, etc... |
When are you going to add support for sorting by number of downloads in descending order? |
I am surprised that Nuget doesn't support sorting especially by downloads.... |
Note..one of the issues for this (https://developercommunity.visualstudio.com/content/problem/56659/nuget-management-window-nuget-updates-can-not-be-s.html ) complained that the updates tab isn't sorted by name by default...and can't change to being sorted by name as well. |
Any progress on this? |
Yet another request to sort 'Browse' tab by download counts. Originally posted by @msd-kharazi in #1739 (comment) |
The browse tab functionality is driven by search behavior. If the servers don't return results sorted by say downloads, the client wouldn't be able to do too much. Also, keep in mind the challenges for the "All" behavior, do they add up? Pick the largest etc. Right now the all tab displays partial results and it wouldn't care about the download count. Alternatively, certain "search by" could be available on individual sources only. |
No description provided.
The text was updated successfully, but these errors were encountered: