-
Notifications
You must be signed in to change notification settings - Fork 843
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
ide/lsp.client add opened documents after start #3812
Labels
kind:feature
A feature request
Comments
vieiro
added
kind:feature
A feature request
needs:triage
Requires attention from one of the committers
labels
Mar 19, 2022
ide/lsp.client does indeed tell the server about opened files on start, problem is that we have many different RequestProcessors for feature, and we may want to have one RequestProcessor per server (so it's easier to send requests in proper order). |
vieiro
added a commit
to vieiro/netbeans-cnd
that referenced
this issue
Apr 13, 2022
- Admits all SemanticTokenTypes and SemanticTokenModifiers in the LSP specification. - Adds a RequestProcessor in LSPBindings to: - Request from different LSP clients (TypeScript and C++, for instance) do not share a single thread, blocking each other. - Requests to the same LSP client (C++, for instance) are properly sequenced, so that LSPBindings, BreadcrumbsImpl, LanguageClientImpl and TextDocumentSyncServerCapabilityHandler work together in harmony (see apache#3812)
Merged
vieiro
added a commit
to vieiro/netbeans-cnd
that referenced
this issue
Apr 30, 2022
- Each LSP server has its own (single thread) RequestProcessor, so a slow LSP server doesn't slow down others. - All LSP features use this very same RequestProcessor. On LSP server startup all opened files are sent to the server, so the next requests (BreadcrumbsImpl, etc.) don't confuse the LSP server (see apache#3812).
matthiasblaesing
added a commit
to matthiasblaesing/netbeans
that referenced
this issue
Sep 16, 2024
…ment sychronously on startup - Run open document registration in LSP servers synchronously with initialization - Instead of spinning custom RequestProcessors use the existing queue on the LSP Bindings via runOnBackground - Where possible drop RequestProcessor usage and run code directly Closes: apache#3812
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
ide/lsp.client could make sure that the lsp server is informed about currently opened files in the editor immediately after start
Use case/motivation
The LSP server (clangd in this case) complaining about a request of semantic highlighting for files not previously opened with
didOpen
:Related issues
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: