NuGet/Home

JSON output for dotnet nuget why command

Open

#13 927 ouverte le 14 nov. 2024

Voir sur GitHub
 (0 commentaires) (2 réactions) (0 assignés)HTML (292 forks)batch import
Priority:3Type:Featurehelp wanted

Métriques du dépôt

Stars
 (1 459 stars)
Métriques de merge PR
 (Merge moyen 464j 23h) (1 PR mergée en 30 j)

Description

NuGet Product(s) Involved

NuGet.exe

The Elevator Pitch

The output of dotnet nuget why command is incredibly useful for problems like component governance. Right now, it only supports printing output to the terminal. It would very useful to have a mode that supports putting the output to a JSON file, and, if possible, having a set of public classes that we can deserialize that output to.

Additional Context and Details

As my team works on problems like Component Governance, being able to analyze how transitive packages are introduced (as well as how those dependencies shake out between projects) is a key part of the puzzle and I think the output of this command can help a ton.

Guide contributeur