Repository navigation
sorting find-package-versions #886
Description
Activity
Argh. So I assume the nuget team broke the order again.
On Jun 21, 2015 2:49 AM, "Cameron Taggart" notifications@github.com wrote:I was expecting find-package-versions to display the display the latest
version first like the documentation describes here:
http://fsprojects.github.io/Paket/paket-find-package-versions.htmlUnfortunately, I get this:
[image: image]
https://cloud.githubusercontent.com/assets/80104/8269892/910f0024-1774-11e5-9200-1bb43628fed4.pngI've got tab completion working for #873
#873, but it would work a
whole lot better with this fixed.—
Reply to this email directly or view it on GitHub
#886.This is not fixed in
1.16.0.
Should it be possible to specify the sort order using
--sort ascendingand--sort descending(with--sort descendingbeing the default)?If we follow the current parameter naming convention of
find-package-versions, the parameter should maybe be namedsort ascending/sort descending, which I personally favor over--sort ascending.question is if anybody really needs this param.
btw: this issue is fixed in 1.17. - I must have been drunk yesterday when I accidentally added the "fix" to the
find-packagefunction and broke that one too.If you ask who needs this: Noone, really, because you just have to
.Reverse()the resulting list of versions (if we assume nomaxargument). The only usage I can think of is scripting support, but there you most likely want to get the newest versions anyway.
I was expecting find-package-versions to display the display the latest version first like the documentation describes here:
http://fsprojects.github.io/Paket/paket-find-package-versions.html
Unfortunately, I get this:
I've got tab completion working for #873, but it would work a whole lot better with this fixed.