microsoft / microsoft/language-server-protocol

Support multiple output channels for log message notifications

Open
#1,885 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature-request new request
Dominant language
TypeScript
Stars
13k
Forks
1k
Avg merge
6d 1h
Merged PRs (30d)
10

Description

Proposing a feature to allow log message notifications to report their output to a specific channel. These could be used to differentiate the output between multiple long and short lived tasks that may be run by the same language server at any given time.

Currently, since all log message notifications end up mixed in the same output channel, it can be difficult to use for cases such as implementing a run of a build that produces its own linear output that should be collected and viewed separately from any of the server's other output.

Another option could be something more like a show document request that displays text in a more read only manner, for example in a display more similar to the view in which VS code outputs test run progress.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the protocol's log message notification behavior and the alternative show document request described in the issue, then compare how VS Code presents test-run progress. Define the protocol scope and expected channel behavior before identifying the affected specification entry points and validation needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.