microsoft / microsoft/vscode-languageserver-node
Allow customizing the name of the option for enabling tracing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 404
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 14
Description
Feature request
AFAIK the only way to enable tracing for messages exchanged between the client and server is to set <langId>.trace.server to verbose. It would be nice if we could specify a custom configuration option from where to retrieve this value. For example, I'd like to use something like <langId>.lsp.tracing, because it better aligns with other config options of my extension.
I am willing to submit a PR that implements the feature if that is something you'd be open to.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the handling of .trace.server in the repository and inspect the related configuration and tracing entry points. Determine how a custom option should be supplied while preserving the existing option, then verify that tracing follows the custom setting and the default behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100