-
Notifications
You must be signed in to change notification settings - Fork 288
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
Implement sourcekit-lsp --version
option
#1496
base: main
Are you sure you want to change the base?
Conversation
Currently `sourcekit-lsp --version` is an invalid option, which makes it harder to debug issues with SourceKit-LSP, as one can't even easily know which version is installed: ``` ❯ sourcekit-lsp --version Error: Unknown option '--version' ```
@swift-ci test |
@swift-ci test macos |
1 similar comment
@swift-ci test macos |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you
@swift-ci test macos |
1 similar comment
@swift-ci test macos |
@swift-ci test |
1 similar comment
@swift-ci test |
@swift-ci test |
@@ -10,6 +10,8 @@ | |||
// | |||
//===----------------------------------------------------------------------===// | |||
|
|||
import ArgumentParser | |||
import struct Basics.SwiftVersion |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer to not add a dependency on SwiftPM for this. I’ve been trying to isolate SourceKit-LSP’s dependency on SwiftPM recently and would prefer to not add a new one. I still don’t know what the best solution would be. I wrote down some of my thoughts in #1424 (comment).
Currently
sourcekit-lsp --version
is an invalid option, which makes it harder to debug issues with SourceKit-LSP, as one can't even easily know which version is installed: