Fix SwiftPM's dropdown showing on projects disabling the SwiftPM integration #2011
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
rockbruno
force-pushed
the
rochab/swiftpm-disable
branch
from
62634bb to
a3ff6cf
Compare
rockbruno
requested review from
0xTim,
adam-fowler and
award999
as code owners
matthewbastien
requested changes
Dec 18, 2025
Member
matthewbastien
left a comment
matthewbastien
left a comment
There was a problem hiding this comment.
Thank you for fixing this! Just a couple comments that need to be fixed before we can merge.
rockbruno
force-pushed
the
rochab/swiftpm-disable
branch
from
a3ff6cf to
9456c0b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Description
We use a BSP with
disableSwiftPMIntegrationset to true, but we still had a couple of SwiftPM features showing around. This seemed to be because the extension was returning an empty package instead ofundefinedlike it would if the package happened to not exist at all. Making it returnundefinedfixed the issue.Tasks