[6.3] Allow opting in to using the new SwiftPM BSP when opening a package #2392
Conversation
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
owenv
requested review from
ahoppen,
hamishknight and
rintaro
as code owners
Contributor
Author
|
@swift-ci test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Explanation:
Add an opt-in flag to configure SourceKit-LSP to use the SwiftPM build server for package functionality
Scope:
Cherrypicks an opt in flag for integrating the new build server using the existing external BSP functionality
Original PR:
#2378
Risk:
Low. This is a small change to the build system backend selection which is entirely opt-in.
Testing:
Existing CI tests
Reviewers:
@ahoppen