Skip to content
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

adjust to latest SwiftPM APIs #741

Merged

Conversation

tomerd
Copy link
Contributor

@tomerd tomerd commented May 2, 2023

motivation: support changes in SwiftPM underlying path APIs

changes:

  • adjust call sites in SwiftPMWorkspace to use SwiftPM's path

motivation: support changes in SwiftPM underlying path APIs

changes:
* adjust call sites in SwiftPMWorkspace to use SwiftPM's path
@tomerd
Copy link
Contributor Author

tomerd commented May 2, 2023

tested via swiftlang/swift-package-manager#6509

Comment on lines +31 to +32
import struct Basics.AbsolutePath
import struct Basics.TSCAbsolutePath
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What’s the rule about using TSCAbsolutePath vs. AbsolutePath? Or which features will one support but not the other?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we are slowly transitioning SwiftPM code base off of TSC. I wanted to keep the change set smaller so lets all the LSP code using the TSC version, but since some of SwiftPM public APIs are now using SwiftPM's AbsolutePath we need do some bridging in SwiftPMWorkspace. eventually all of SwiftPM public APIs will be based on swift-system Path so we will be aligned again, this is the first step to get there

@tomerd
Copy link
Contributor Author

tomerd commented May 5, 2023

@swift-ci test

@tomerd tomerd merged commit 90fd3ad into swiftlang:main May 5, 2023
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