aboutsummaryrefslogtreecommitdiff
path: root/docs/dev/lsp-features.md
Commit message (Collapse)AuthorAgeFilesLines
* Remove executeCommandProvider: apply_code_action.Michael Bolin2019-07-111-2/+0
| | | | | | | | | | | | | | | | | | | 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.
* Add to LSP featureskjeremy2019-04-231-1/+1
|
* fix docsAleksey Kladov2019-04-211-1/+1
|
* introduce docs dirAleksey Kladov2019-03-201-0/+74