Skip to content
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

dotnet list package does not indicate presence of a deprecated package #8620

Closed
anangaur opened this issue Sep 23, 2019 · 8 comments
Closed
Assignees
Labels
Functionality:ListPackage dotnet.exe list package Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Product:dotnet.exe Type:Bug
Milestone

Comments

@anangaur
Copy link
Member

As part of the PR NuGet/NuGet.Client#2928, it was supposed to put an indication on the presence of a deprecated package with the command dotnet list package. However it doesn't seem to work.

dotnet list package --deprecated works however.

Feature issue: #2867

@nkolev92
Copy link
Member

Can you clarify what the indicator of the presence of a deprecated package is?

The appearance of the legend or?

@nkolev92 nkolev92 added Functionality:ListPackage dotnet.exe list package Type:Bug labels Sep 23, 2019
@nkolev92 nkolev92 added this to the 5.4 milestone Sep 23, 2019
@anangaur
Copy link
Member Author

anangaur commented Sep 23, 2019

Thats right. It was supposed to do this:

Right now it doesn't put the legend.

@xavierdecoster
Copy link
Member

Looks like a mismatch in expectations: marking deprecated packages as part of dotnet list package (without --outdated or --deprecated switch) wasn't part of the spec.

If dotnet list package already shows the deprecated packages, then what's the purpose of dotnet list package --deprecated? How do they differ?

@nkolev92
Copy link
Member

Rereading now I agree with @xavierdecoster, dotnet list package itself should remain offline.

@anangaur
Copy link
Member Author

The spec calls out that we needed to show the deprecation info even as part of --outdated albeit with minimal flagging. I dont think it does that today:

> dotnet list package --outdated

The following sources were used:
   https://api.nuget.org/v3/index.json

Project `My.Test.Project` has the following updates to its packages
   [netcoreapp3.0]:
   Top-level Package      Requested   Resolved   Latest
   > Newtonsoft.Json      11.0.2      11.0.2     12.0.2

But --deprecated shows the deprecated package:

> dotnet list package --deprecated

The following sources were used:
   https://api.nuget.org/v3/index.json

Project `My.Test.Project` has the following deprecated packages
   [netcoreapp3.0]:
   Top-level Package      Resolved   Reason(s)   Alternative
   > My.Sample.Lib        6.0.0      Legacy      My.Awesome.Package

@nkolev92
Copy link
Member

Ahh, maybe that happens because My.Sample.Lib is not outdated?

@rrelyea
Copy link
Contributor

rrelyea commented Oct 31, 2019

Can you folks conclude?

@nkolev92 nkolev92 added Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. and removed Triage:NeedsTriageDiscussion labels Apr 30, 2020
@nkolev92
Copy link
Member

This was something that was cleared up in the context of adding vulnerability to dotnet list package https://github.com/NuGet/Home/blob/dev/proposed/2020/PackageVulnerability/DotnetListPackageVulnerable.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Functionality:ListPackage dotnet.exe list package Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Product:dotnet.exe Type:Bug
Projects
None yet
Development

No branches or pull requests

5 participants