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) <noreply@anthropic.com>
This commit is contained in:
@@ -55,7 +55,7 @@ export class LSPClientConnection extends LSPClientTransport {
|
|||||||
},
|
},
|
||||||
},
|
},
|
||||||
},
|
},
|
||||||
...this.server.initialization,
|
initializationOptions: this.server.initialization,
|
||||||
})
|
})
|
||||||
this.sendNotification("initialized")
|
this.sendNotification("initialized")
|
||||||
this.sendNotification("workspace/didChangeConfiguration", {
|
this.sendNotification("workspace/didChangeConfiguration", {
|
||||||
|
|||||||
Reference in New Issue
Block a user