NuGet/Home

JSON output for dotnet nuget why command

Open

#13.927 geöffnet am 14. Nov. 2024

Auf GitHub ansehen
 (0 Kommentare) (2 Reaktionen) (0 zugewiesene Personen)HTML (292 Forks)batch import
Priority:3Type:Featurehelp wanted

Repository-Metriken

Stars
 (1.459 Stars)
PR-Merge-Metriken
 (Durchschn. Merge 464T 23h) (1 gemergte PR in 30 T)

Beschreibung

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.

Contributor Guide