-
Notifications
You must be signed in to change notification settings - Fork 327
Issues: microsoft/vscode-languageserver-node
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Clearing existing diagnostics when a watched configuration file is modified
bug
Issue identified by VS Code Team member as probable bug
window/showDocument cannot show two documents because of preview mode
info-needed
Issue requires more information from poster
#1588
opened Nov 15, 2024 by
rcjsuen
LanguageClient get stuck in starting state with socket transport kind
bug
Issue identified by VS Code Team member as probable bug
revealOutputChannelOn not taking effect for Issue identified by VS Code Team member as probable bug
outputChannel
for server initiated messages
bug
Overflow value(exceeding uinteger) passed into jsonrpc but still work
feature-request
Request for new features or functionality
help wanted
Issues identified as good community contribution opportunities
ReadableStreamMessageReader.listen
should register data
handler once per readeable
bug
Support notification progress instead of only status bar
feature-request
Request for new features or functionality
help wanted
Issues identified as good community contribution opportunities
client.needsStop() and client.stop() disagree on whether it's valid to call stop()
bug
Issue identified by VS Code Team member as probable bug
Allow customizing the name of the option for enabling tracing
feature-request
Request for new features or functionality
Stopped client can recreate its OutputChannel
bug
Issue identified by VS Code Team member as probable bug
Document links not rendering in editor despite being correctly returned from the language server
info-needed
Issue requires more information from poster
#1492
opened Jun 6, 2024 by
benjamin-t-santos
Extra semanticTokens requests in a multiroot workspace
bug
Issue identified by VS Code Team member as probable bug
info-needed
Issue requires more information from poster
Option to control Request for new features or functionality
workspaceFolders
in InitializeParams
feature-request
How to support CompletionItemKind#Color in LSP client completion?
feature-request
Request for new features or functionality
Consider Adding a Request for new features or functionality
help wanted
Issues identified as good community contribution opportunities
ExtensionVersion
to ClientInfo
feature-request
Conform to the recommendation in the standard for the socket argument, which is currently Request for new features or functionality
--socket
instead of --port
feature-request
Add support for Request for new features or functionality
NotebookEdit
in WorkspaceEdit
feature-request
Support bun as a runtime for language servers
feature-request
Request for new features or functionality
help wanted
Issues identified as good community contribution opportunities
Catching unhandled exceptions when starting language server by LanguageClient
feature-request
Request for new features or functionality
help wanted
Issues identified as good community contribution opportunities
meta model should also include a programmatic description of the LSP state machine
feature-request
Request for new features or functionality
metaModel
Allow initializationOptions, fillInitializeParams, etc to be async
feature-request
Request for new features or functionality
help wanted
Issues identified as good community contribution opportunities
Tuple members should be optionally named
feature-request
Request for new features or functionality
metaModel
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.