Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Every time I call client.setTrace(Trace.Verbose), VSCode sends a new { "$/setTrace", "params": { "value": "off" } } notification to the language server.
I'm impressed at how well Microsoft separates its talented language devs from everyone else. None of their other products inherit the tiniest fragment of the reliability of their languages.
A dev can dream, right...?
When you try to dive deep into the docs.
oops
VSCode is doing really strange things to my language server, in such variety that I'm starting to suspect that it's simply incorrect because it's very unlikely that I'd misunderstand so many distinct things at once.
- The trace level is verbose, yet VSCode absolutely spams the LS with trace: off requests
- the capability update request I used to set file watchers never gets a response even though the standard clearly states that all requests must get responses or progress reports quickly, and I'm not getting file updates even after vscode responds to a file system change. By the way, if file watching is a capability, why can't I set it in the protocol handshake with all the other capabilities?
- my semantic token provider (used for syntax highlighting) is simply ignored, no requests, no errors
- the debug console is spamming editor internal errors
rant
lsp
langdev
vscode
orchid