This repository was archived by the owner on Feb 26, 2026. It is now read-only.
fix: do not map project target dependency to an underlying type#112
Merged
fix: do not map project target dependency to an underlying type#112
Conversation
pepicrft
approved these changes
Feb 10, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
I am not 100 % sure why we were mapping project target dependencies to cases such as
.framework, however, this breaks some of the logic intuist. Dependency to cases like.frameworkare only when those products are prebuilt. That's not the case for project target dependencies.Additionally, this simplifies the mapping logic a bit.