-
Notifications
You must be signed in to change notification settings - Fork 695
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
Add RID specific packages to dotnet nuget why
#6154
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. GetAllDependencyGraphsForTarget is getting a little long though.
src/NuGet.Core/NuGet.CommandLine.XPlat/Commands/Why/DependencyGraphFinder.cs
Outdated
Show resolved
Hide resolved
…GraphFinder.cs Co-authored-by: Jonatan Gonzalez <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exciting to see this work being done.
I do think we need more exhaustive testing. I've provided some examples in my other comments.
Bug
Fixes: NuGet/Home#13718
Description
Originally
dotnet nuget why
only showed a path in the dependency graph, only for RIDless packages only. This PR makes sure we show RID specific packages in the tree as well. This is done by creating a tree for each RID and framework combination. Each combination will have its own tree. For example, if a user hasnet9.0
framework andwin-x64
RID, we will have a tree fornet 9.0 / win-x64
net 9.0
PR Checklist
dotnet nuget why
graphs RID specific packages Home#13944