Skip to content

[5.5] SourceKitLSP: properly handle paths on Windows #397

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
merged 2 commits into from
May 25, 2021

Conversation

compnerd
Copy link
Member

This corrects the path identification to include Windows paths properly.
Although this is not entirely ideal due to the platform specific code,
but avoids crashing the SourceKit LSP server if it encounters a space in
the path.

This corrects the path identification to include Windows paths properly.
Although this is not entirely ideal due to the platform specific code,
but avoids crashing the SourceKit LSP server if it encounters a space in
the path.
@compnerd compnerd requested a review from benlangmuir as a code owner May 24, 2021 20:21
@compnerd
Copy link
Member Author

@swift-ci please test

@compnerd
Copy link
Member Author

@benlangmuir I'd like to nominate this for the 5.5 cycle as it really helps improve the stability of SK-LSP on Windows. It should be low risk as the non-Windows path is unchanged.

@compnerd
Copy link
Member Author

@swift-ci please test Linux platform

@compnerd compnerd changed the title SourceKitLSP: properly handle paths on Windows [5.5] SourceKitLSP: properly handle paths on Windows May 25, 2021
Correct the polarity of the check.  The path being a UNC path or having a drive letter indicates that it *is* a path, as opposed to the inverted representation that was accidentally committed.
@compnerd
Copy link
Member Author

@swift-ci please test

@benlangmuir benlangmuir merged commit 6bfa17e into swiftlang:release/5.5 May 25, 2021
@compnerd compnerd deleted the windows-5-5-stable branch May 25, 2021 22:24
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.

2 participants