Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Sorted by recent installs

See original GitHub issue

What is the logic is that NuGet uses to rank its unsearched results? I thought it was recent installs (nuget.org/packages says “Sorted by recent installs”) which meant the number of Install hits in the last 6 weeks, but that doesn’t appear to be the case.

For example Microsoft.AspNet.WebPages is ranked ahead of Microsoft.AspNet.WebApi.Client and AutoMapper even though it has less installs.

Is this a bug, a delay in updating, or is there some different logic at work?

Issue Analytics

State:
Created 8 years ago
Comments:6 (1 by maintainers)

Top GitHub Comments

1reaction

yishaigalatzercommented, Jan 30, 2016

The importance of the exact order in the list is kinda negligible. I don’t know that we want to spend time researching this. If there is anything of importance feel free to re-raise the issue. Otherwise I’m closing it for lack of interest to the public 😃

0reactions

csharpfritzcommented, Jan 30, 2016

There are other, more interesting initial lists of packages that we could explore in the future.

On Jan 30, 2016, at 11:45, Yishai Galatzer notifications@github.com wrote:

I’m saying the importance of the empty list is pretty much zero. I wish we never had it.

— Reply to this email directly or view it on GitHub.