Fix trace.server option #617
Merged
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
fendor
reviewed
Jun 8, 2022
Collaborator
fendor
left a comment
fendor
left a comment
There was a problem hiding this comment.
Hi, thank you for your PR!
Just a couple of questions, otherwise good to go
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
The trace server option is useful for debugging the JSON messages sent between the LSP client and server. A standardized output format is provided by
vscode-languageclient/node, compatible with this lsp inspector tool.To get the LanguageClient to read the trace server option from the config, the
idpassed to the language client needs to match the section used ingetConfiguration. I also add a verbose option to the config, since it is supported by the LanguageClient.