You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apple Swift version 6.0.2 (swiftlang-6.0.2.1.2 clang-1600.0.26.4)
Platform
macOS 15
Editor
VS Code
Description
If I open a swift package and set one of its dependencies to be in edit mode the background indexing ignores this and still tries to index the project as if it is using the version of the dependency in .index-build.
Steps to Reproduce
Open package with dependencies in VSCode
Clone one of its dependencies in a separate folder
Right click on dependency in package dependencies view, select "Use Local Version" and select your local clone of that dependency. This is the equivalent of running `swift package edit -path
In main package right click on symbol from dependency and jump to definition
Note you jump to version in .index-build and not the local version
This is most likely caused by the fact that the package edit commands edit the workspace-state.json file and these changes are not propagated to the .index-build folder.
Logging
No response
The text was updated successfully, but these errors were encountered:
The fix for this would require a major architectural redesign of how SourceKit-LSP interacts with SwiftPM’s workspace state and integrates with SwiftPM’s build folder. It’s out-of-scope for 6.1.
Swift version
Apple Swift version 6.0.2 (swiftlang-6.0.2.1.2 clang-1600.0.26.4)
Platform
macOS 15
Editor
VS Code
Description
If I open a swift package and set one of its dependencies to be in edit mode the background indexing ignores this and still tries to index the project as if it is using the version of the dependency in
.index-build
.Steps to Reproduce
.index-build
and not the local versionThis is most likely caused by the fact that the package edit commands edit the
workspace-state.json
file and these changes are not propagated to the.index-build
folder.Logging
No response
The text was updated successfully, but these errors were encountered: