Open popnfloss opened 4 years ago
As far as I can see, with the edit of synchronization method (listing OBSERVED_SETTINGS
in src/rls.ts) have broken the application of the falsy (i.e., false, null, 0, etc) values to the didChangeConfiguration
notification, as VSCode-LanguageServer-Client checks it non-strictly.
(The same happens to "rust.all_targets": false
, by the way).
I'm not sure whether this is intentional on the languageserver-client side, but immediately patching the aforelinked line in your .vscode/extensions/rust-lang.rust-X.X.X/node_modules/vscode-languageclient/lib/client.js
to if (config !== null)
allows those falsy values to propagate to the Rust Language Server.
Turning off warnings has no effect.