squiid/rust
1
0
Fork 0
Code Issues Pull requests Projects Activity

Merge #7012

Browse source 
7012: Document, how to view config in effect r=matklad a=matklad

bors r+
🤖

Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>
This commit is contained in:
bors[bot] 2020-12-23 07:47:40 +00:00 committed by GitHub
commit 58b6763f20
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
crates/rust-analyzer/src/config.rs
View file

@ -349,12 +349,12 @@ impl Config {
res
}
pub fn update(&mut self, json: serde_json::Value) {
log::info!("Config::update({:#})", json);
log::info!("updating config from JSON: {:#}", json);
if json.is_null() || json.as_object().map_or(false, |it| it.is_empty()) {
return;
}
self.do_update(json);
log::info!("Config::update() = {:#?}", self);
log::info!("updated config: {:#?}", self);
}
fn do_update(&mut self, json: serde_json::Value) {
let data = ConfigData::from_json(json);

3
docs/user/manual.adoc
View file

@ -302,6 +302,9 @@ If the LSP binary is not available, GNOME Builder can install it when opening a
rust-analyzer is configured via LSP messages, which means that it's up to the editor to decide on the exact format and location of configuration files.
Please consult your editor's documentation to learn how to configure LSP servers.
To verify which configuration is actually used by rust-analyzer, set `RA_LOG` environment variable to `rust_analyzer=info` and look for config-related messages.
Logs should show both the JSON that rust-analyzer sees as well as the updated config.
This is the list of config options rust-analyzer supports:
include::./generated_config.adoc[]