vim.lsp client configuration propagation to active servers

LSP Configuration Synchronization

Neovim's built-in LSP client (vim.lsp) manages communication with language servers via JSON-RPC. While buffers attach to clients based on filetype, the propagation of configuration changes to a running server is not an automated process.

The LSP specification defines the workspace/didChangeConfiguration notification to inform servers of updated settings. However, modifying the Lua configuration table within Neovim does not natively trigger this notification to the attached client.

This creates a gap between the local editor state and the server's active configuration, requiring a decision on whether to manually implement notification logic or restart the client entirely.

• Does Neovim provide a built-in mechanism to automatically emit workspace/didChangeConfiguration when vim.lsp.config is updated?
• What is the recommended approach for synchronizing dynamic configuration changes without forcing a full client restart?