Skip to content

Conversation

@michaelgruenewald
Copy link
Contributor

@michaelgruenewald michaelgruenewald commented Dec 17, 2025

In #20837 the extension config API was added. That change sends a configuration to the LSP, that may have been extended by other VS Code extensions. However, there are multiple code path for the rust-analyzer LSP to fetch the configuration: via the initialConfig that was changed in the original PR, and via an LSP request that was missed in the original PR. This fixes that by using the same config structure instead of letting the generic vscode-languageclient code handle it. There is only one user of that specific LSP request in rust-analyzer here, so we don't need the extra overhead of supporting other configuration sections.

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Dec 17, 2025
@michaelgruenewald michaelgruenewald force-pushed the fix-lsp-configuration-request branch from 43ffcf9 to e1c9eac Compare December 17, 2025 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants