Skip to content

Support LSP workspace/didChangeConfiguration in addition to initializationOptions #2180

Closed

Description

@garrett-hopper

Currently custom LSPs can only be configured with initialize which passes initializationOptions as part of the LSP initialization call.
Some LSP servers require settings to be passed in workspace/didChangeConfiguration instead. (Namely tailwindcss-language-server is what I'm running into at the moment)

workspace/didChangeConfiguration appears to be the more standard way to configuring LSP servers (Neovim passes settings as this, which the majority of configurations in nvim-lspconfig utilize as opposed to of init_options).

Activity

  1. garrett-hopper commented on Aug 22, 2025

    @garrett-hopper
    Author

    Notably, terraform-ls requires initializationOptions instead, so both are needed. (lspconfig/doc/configs.md#terraformls)

  2. self-assigned this
    on Aug 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions