From 04637ff0f1a8a58833fc284af20e69071bad7885 Mon Sep 17 00:00:00 2001 From: Tony Park Date: Fri, 20 Mar 2026 02:11:54 +0900 Subject: [PATCH] fix(lsp): wrap initialization config in initializationOptions field The LSP `initialize` request expects custom server options in the `initializationOptions` field, but the code was spreading `this.server.initialization` directly into the root params object. This caused LSP servers that depend on `initializationOptions` (like ets-language-server, pyright, etc.) to not receive their configuration. Closes #2665 Co-Authored-By: Claude Opus 4.6 (1M context) --- src/tools/lsp/lsp-client-connection.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/tools/lsp/lsp-client-connection.ts b/src/tools/lsp/lsp-client-connection.ts index b9eec9ded..e75a681c7 100644 --- a/src/tools/lsp/lsp-client-connection.ts +++ b/src/tools/lsp/lsp-client-connection.ts @@ -55,7 +55,7 @@ export class LSPClientConnection extends LSPClientTransport { }, }, }, - ...this.server.initialization, + initializationOptions: this.server.initialization, }) this.sendNotification("initialized") this.sendNotification("workspace/didChangeConfiguration", {