Document --trace and --protocol-log-level server CLI arguments - #50
Merged
Conversation
PR #42 (F41) added --trace and --protocol-log-level alongside the existing --log-level, and wired per-IDE defaults into the VS extension's server launch and VS Code's reqnroll.trace.server setting, but none of the docs described them. Document the flags, their defaults, the --trace precedence against InitializeParams.Trace/$/setTrace, and how each IDE client sets them, in README.md and the four CONTRIBUTING.md guides. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Fixes #46
PR #42 (F41: LSP trace support) added two new command-line arguments to the LSP server (
Reqnroll.IdeSupport.LSP.Server.exe), alongside the existing--log-level, but none of the top-level or per-client docs described them. This PR documents:--trace <Off/Messages/Verbose>and--protocol-log-level <Off/Error/Warning/Info/Verbose>alongside--log-level, insrc/LSP/CONTRIBUTING.md, including the--traceprecedence order (CLI default →InitializeParams.Trace→$/setTrace), read directly fromProgram.cs'sConfigureServer/ResolveInitialTrace.LspServerConnectionService.ServerArguments's DEBUG vs. RELEASE defaults insrc/VisualStudio/CONTRIBUTING.md, and that VS currently has no end-user UI to change these at runtime.reqnroll.trace.serverVS Code setting insrc/VSCode/CONTRIBUTING.md, and how it maps to both the wire-level trace (InitializeParams.Trace/$/setTrace, handled byvscode-languageclientitself) and the server's--log-levelCLI argument (viatraceServerToLogLevel()) — VS Code does not pass--traceor--protocol-log-levelat all.README.mdandCONTRIBUTING.md.Test plan
src/LSP/Reqnroll.IdeSupport.LSP.Server/Hosting/Program.cs,src/VisualStudio/Reqnroll.IdeSupport.VisualStudio.Extension/LspInterception/LspServerConnectionService.cs, andsrc/VSCode/src/lspInspectorLogger.ts/extension.ts.🤖 Generated with Claude Code