Repository navigation
Preserve Swift dependency requirements and target scopes - #120
Merged
Merged
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
andrew
force-pushed
the
fix/swift-dependency-parsing
branch
from
October 21, 2026 10:11
b68c9fb to
699a0f8
Compare
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Swift manifests could lose exact and branch requirements, range upper bounds and registry dependencies, while comments could produce false dependencies. Parse literal declarations and explicit target usage, recognize version-specific manifests, and preserve pinned revisions from lockfiles.
Keep source repository coordinates separate from registry identities and distinguish test/build usage where target references permit it. Add public parser tests with multiline declarations, comments and a transitive lockfile pin, and document the output contract and static extraction limits.