microsoft / microsoft/vscode-markdown-languageserver
Language Server sends `window/logMessage` events with illegal message type
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 45
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
I am trying to integrate the markdown language server with Eclipse via LSP4J which chokes during communication because the language server sometimes sends log messages of type object instead of string which violates the LSP spec which states the message parameter must be of type string.
An example:
{"jsonrpc":"2.0","method":"window/logMessage","params":{"type":4,"message":{}}}
As a workaround I am currently patching the JSON RPC messages in-flight via a local proxy but would be nice if that was not necessary.
Contributor guide
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 reproducing the reported window/logMessage payload and inspect the TypeScript language-server code that emits these events. Confirm which path can send an object as message; done means every window/logMessage message is a string and the example communication succeeds with Eclipse LSP4J.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100