aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_lsp_server/src/caps.rs
Commit message (Collapse)AuthorAgeFilesLines
* insert space after `->`Aleksey Kladov2019-10-251-1/+1
|
* Added test for check doc strings in crates.Alexander Andreev2019-09-301-0/+2
| | | | #1856
* lsp-types 0.61.0kjeremy2019-09-031-0/+1
|
* Remove executeCommandProvider: apply_code_action.Michael Bolin2019-07-111-6/+4
| | | | | | | | | | | | | | | | | | | 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.
* allow rustfmt to reorder importsAleksey Kladov2019-07-041-3/+4
| | | | | | This wasn't a right decision in the first place, the feature flag was broken in the last rustfmt release, and syntax highlighting of imports is more important anyway
* Basic resolution for ADTkjeremy2019-04-231-2/+2
|
* switch to official extend selection APIAleksey Kladov2019-04-211-1/+2
|
* reformat the worldAleksey Kladov2019-02-081-12/+8
|
* Implement lens for impls and support resolving lenses.Jeremy Kolb2019-02-041-1/+1
|
* Go to Implementation for structs and enumsJeremy Kolb2019-01-301-2/+2
|
* switch to lsp-typesAleksey Kladov2019-01-141-1/+1
|
* Code lens support for running testsJeremy A. Kolb2019-01-111-2/+4
|
* add "." as a trigger char on type formattingSimon Vandel Sillesen2019-01-061-1/+1
|
* Implement DocumentHighlightDJMcNab2018-12-311-1/+1
|
* Add support for formatting entire document with rustfmtAleksander Vognild Burkow2018-12-291-1/+1
| | | | | | Attempting to format a document when rustfmt isn't installed will result in an error being returned to the frontend. An alternative implementation would be returning zero replacements.
* Add . to trigger charactersFlorian Diebold2018-12-251-1/+1
|
* Use `:` as a trigger character for completionAleksey Kladov2018-11-211-1/+1
| | | | | | | | | Note that VSCode asks for completion after *first* `:` as well: use crate: we use hacks to protect against that, and to give completions only after the second `:`.
* Show documentation for hover requestsJeremy A. Kolb2018-11-071-1/+1
|
* Use closing paren as a trigger characterJeremy A. Kolb2018-11-051-1/+1
| | | | | This seems counter-intuitive based on the concept of "trigger character" but it provides a better function signature experience.
* Reformat allAleksey Kladov2018-10-311-5/+5
|
* Handle renaming of local variablesJeremy A. Kolb2018-10-181-2/+4
|
* Implement Find All References for local variablesJeremy A. Kolb2018-10-181-1/+1
|
* Cargo FormatJeremy A. Kolb2018-10-161-11/+5
| | | | Run `cargo fmt` and ignore generated files
* Language Server: textDocument/signatureHelpJeremy A. Kolb2018-10-111-1/+4
| | | | | | | | | | Implements a pretty barebones function signature help mechanism in the language server. Users can use `Analysis::resolve_callback()` to get basic information about a call site. Fixes #102
* Support LSP 3.13Jeremy A. Kolb2018-09-231-1/+5
|
* rename all thingsAleksey Kladov2018-09-161-0/+49
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-01 17:21:31 +0000