aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src/test/fixtures/rust-diagnostics/warning
diff options
context:
space:
mode:
authorMichael Bolin <[email protected]>2019-07-11 06:49:29 +0100
committerMichael Bolin <[email protected]>2019-07-11 06:49:35 +0100
commite81a47b8ebce9bcf680b15c6e0c1e879200f75df (patch)
treeb1cb42753d44169529ba62353746ce964bab5c7b /editors/code/src/test/fixtures/rust-diagnostics/warning
parenta814883cd40be772d52bb8e7424326021fdb0e0e (diff)
Remove executeCommandProvider: apply_code_action.
This appears to have been introduced ages ago in https://github.com/rust-analyzer/rust-analyzer/commit/be742a587704f27f4e503c50f549aa9ec1527fcc but has since been removed. As it stands, it is problematic if multiple instances of the rust-analyzer LSP are launched during the same VS Code session because VS Code complains about multiple LSP servers trying to register the same command. Most LSP servers workaround this by parameterizing the command by the process id. For example, this is where `rls` does this: https://github.com/rust-lang/rls/blob/ff0b9057c8f62bc4f8113d741e96c9587ef1a817/rls/src/server/mod.rs#L413-L421 Though `apply_code_action` does not seems to be used, so it seems better to delete it than to parameterize it.
Diffstat (limited to 'editors/code/src/test/fixtures/rust-diagnostics/warning')
0 files changed, 0 insertions, 0 deletions