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

Never infer implicit reference for existing direct reference #352

Merged
merged 1 commit into from
Mar 19, 2023

Conversation

kzu
Copy link
Member

@kzu kzu commented Mar 19, 2023

We should never traverse and infer implicit transitive dependencies for packages that are already directly referenced by the project.

This fixes the scenario where the project has a direct dependency to a package and another direct dependency has a transitive dependency to the same one. By inferring the latter as an implicit dependency, we overwrite the pack attributes of the former.

@kzu kzu added the bug Something isn't working label Mar 19, 2023
We should never traverse and infer implicit transitive dependencies for packages that are already directly referenced by the project.

This fixes the scenario where the project has a direct dependency to a package and another direct dependency has a transitive dependency to the same one. By inferring the latter as an implicit dependency, we overwrite the pack attributes of the former.
@kzu kzu force-pushed the dev/FixImplicitTransitive branch from 303f0cf to 1fd3101 Compare March 19, 2023 23:22
@kzu kzu enabled auto-merge (rebase) March 19, 2023 23:23
@kzu kzu merged commit 0fab569 into main Mar 19, 2023
@kzu kzu deleted the dev/FixImplicitTransitive branch March 19, 2023 23:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant