microsoft/language-server-protocol

Update tutorial with location of trace.server config

Open

#1,588 opened on Nov 20, 2022

View on GitHub
 (7 comments) (0 reactions) (0 assignees)HTML (12,810 stars) (956 forks)batch import
clarificationhelp wanted

Description

Given this part from the tutorial (sorry - but it forwards to this repo for asking questions):

For lsp-sample, you can set this setting: "languageServerExample.trace.server": "verbose". Now head to the channel "Language Server Example". You should see the logs:

I've tried adding this option to any of the package.json files, as well as .vscode/settings.json (as per this source). I know there's a similar SO post but the author ended up creating their own output channel. Instead, I'd simply like to find the appropriate location. Just wondering whether I'm missing something very obvious or this part of the tutorial should be corrected. If so, is there an alternative way to log messages from the LSP server?

Contributor guide

Tech stack
typescriptjavascript
Domain
documentationdeveloper experience
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
understanding of VS Code settingsbasic LSP knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
The issue points to a specific section in the VS Code LSP tutorial about setting trace.server. The user is unsure where to place the configuration. Investigate the tutorial's instructions and the appropriate settings.json location (e.g., .vscode/settings.json or package.json). Check if the tutorial needs to be updated to clarify the exact location. There are 7 comments that may contain additional clues; review them for suggested solutions.