Skip to content

[6.0] Fix incorrect ConfiguredTargets for Package.swift w/ multiple workspaces #1566

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

Merged

Conversation

plemarquand
Copy link
Contributor

In a project with multiple folders each containing a Package.swift, the
`bestWorkspace` found in `workspaceForDocument(uri:)` was always the
first one encountered.

`fileHandlingCapability(for:)` checks if there are configured targets
for the Package.swift and if there are, the workspace is chosen since
the Package.swift is determined to be part of the workspace. However the
check in `configuredTargets(for:)` always returned a target for any
`Package.swift`, even if that `Package.swift` was not part of the
workspace associated with the BuildSystem.

Ultimately this manifested as code completion not working in all but one
of the Package.swift files in a multi workspace project.

Some work was done in swiftlang#1210 to address swiftlang/vscode-swift#768, which
is where this issue originated from. However while verifying
swiftlang/vscode-swift#768 I found that swiftlang#1210 didn't fully address code
completion of `Package.swift` files in multi workspace projects.
@plemarquand plemarquand requested a review from ahoppen as a code owner July 16, 2024 17:36
@ahoppen ahoppen requested a review from bnbarham July 16, 2024 22:02
@ahoppen
Copy link
Member

ahoppen commented Jul 16, 2024

@swift-ci Please test

@ahoppen ahoppen merged commit f487ebd into swiftlang:release/6.0 Jul 17, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants