Mirrors/rust-analyzer
2
0
Fork 0
mirror of https://github.com/rust-lang/rust-analyzer synced 2024-12-26 13:03:31 +00:00
Code Issues Projects Releases Packages Wiki Activity

Clarify initializationOptions

Browse source
This commit is contained in:
Jeremy Kolb 2020-07-22 10:05:36 -04:00 committed by GitHub
parent 1c7d5f513c
commit 9c0ead30b9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/dev/lsp-extensions.md
View file

@ -11,11 +11,13 @@ If you want to be notified about the changes to this document, subscribe to [#46
## `initializationOptions` ## `initializationOptions`
As `initializationOptions`, `rust-analyzer` expects `"rust-analyzer"` section of the configuration. For `initializationOptions`, `rust-analyzer` expects `"rust-analyzer"` section of the configuration.
That is, `rust-analyzer` usually sends `"workspace/configuration"` request with `{ "items": ["rust-analyzer"] }` payload. That is, `rust-analyzer` usually sends `"workspace/configuration"` request with `{ "items": ["rust-analyzer"] }` payload.
`initializationOptions` should contain the same data that would be in the first item of the result. `initializationOptions` should contain the same data that would be in the first item of the result.
It's OK to not send anything, then all the settings would take their default values. If a language client does not know about `rust-analyzer`'s configuration options it can get sensible defaults by doing any of the following:
However, some settings can not be changed after startup at the moment. * Not sending `initializationOptions`
* Send `"initializationOptions": null`
* Send `"initializationOptions": {}`
## Snippet `TextEdit` ## Snippet `TextEdit`