Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Skip resolved child dependencies in the new resolver if an identical one has already been resolved #6258
base: dev
Are you sure you want to change the base?
Skip resolved child dependencies in the new resolver if an identical one has already been resolved #6258
Changes from 3 commits
63c54d0
498c6a4
05e0562
04b914e
1643a0e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I don't believe it's possible for Parents to be null here since we instantiate it on line 1326 if it is null. So, we should remove the operator to make that clear.
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.
Good idea, I've cleaned up the Parents stuff, let me know if you like it better now.
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.
The ?. operator is still present when dereferencing the Parents which implies that Parents can be null and looking at the changes to the dependency graph item, it looks like there is a case where it can be null. In that case, we'll skip adding the currentDependencyGraphItem.LibraryRangeIndex to the Parents of the childResolvedDependencyGraphItem. This implicit relationship between whether the HashSet is instantiated and whether parents are kept track of worries me for code maintenance and clarity. Is it intentional that we would have a non-root package reference that has null parents that we don't want to keep track of even if the currentDependencyGraphItem has a LibraryRangeIndex? Could this relationship be represented more clearly through tests or could we add a comment? Alternatively, would it make sense to have an empty hash set for the Parents to avoid special casing when it's null or would that break things?