Skip to content

[lsp] Support runtime workspace configuration #502

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
purefunctor merged 2 commits into from
Sep 12, 2026
Merged

[lsp] Support runtime workspace configuration #502

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
418b63b
Support runtime LSP configuration
purefunctor Sep 11, 2026
470f51b
Stabilize LSP test message waits
purefunctor Sep 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 12 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,8 +31,18 @@ iris lsp --stdio --config-file ./iris.json
`--config` and `--config-file` are mutually exclusive and replace `--source-command` and
`--diagnostics-on-open`, `--diagnostics-on-save`, and `--diagnostics-on-change`. File paths are
relative to the process working directory, not the editor's workspace or the configuration file's
directory. Settings are read once before the server starts; changing them requires a restart.
Configuration files are not watched, and LSP configuration notifications do not reload settings.
directory. Startup configuration files are read once and are not watched.

Editors that advertise the LSP `workspace.configuration` capability can provide the same settings
object in the `iris.server` workspace configuration section. Iris requests that section for the first
workspace folder after initialization and requests it again after each
`workspace/didChangeConfiguration` notification; the notification's `settings` value is only an
invalidation signal. Runtime settings take precedence over startup settings. Each response is a
complete runtime layer, so omitted or `null` fields inherit from the startup configuration rather
than from the preceding response. Invalid updates are shown in the editor and leave the last valid
configuration active. Source-setting updates rediscover and reconcile the loaded workspace without
discarding open buffers. Clients without workspace-configuration support continue using only the
startup configuration.

The defaults are:

Expand Down
Loading