aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_lsp_server/src/req.rs
Commit message (Collapse)AuthorAgeFilesLines
* Use proper inlay kindsKirill Bulatov2019-08-041-6/+1
|
* Support destructuring patternsKirill Bulatov2019-07-281-0/+3
|
* Improve inlay hinting for typesKirill Bulatov2019-07-261-0/+1
| | | | | | Add hints for types in for loop expressions. Resolve types for every tuple parameter. Refactor the code.
* Code review fixesKirill Bulatov2019-07-221-0/+27
|
* Remove executeCommandProvider: apply_code_action.Michael Bolin2019-07-111-4/+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.
* Ignore workspace/didChangeConfiguration notifications.Michael Bolin2019-07-111-4/+5
|
* allow rustfmt to reorder importsAleksey Kladov2019-07-041-6/+5
| | | | | | 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
* rename stray id fieldPascal Hertleif2019-05-271-1/+1
|
* Semantic highlighting spikePascal Hertleif2019-05-271-0/+1
| | | | | | | | | | Very simple approach: For each identifier, set the hash of the range where it's defined as its 'id' and use it in the VSCode extension to generate unique colors. Thus, the generated colors are per-file. They are also quite fragile, and I'm not entirely sure why. Looks like we need to make sure the same ranges aren't overwritten by a later request?
* switch to official extend selection APIAleksey Kladov2019-04-211-0/+22
|
* Sends cwd info for runnables and code lensesRoberto Vidal2019-04-141-0/+1
|
* Remove InternalFeedbackVille Penttinen2019-03-051-7/+0
|
* show message in client's UI if workspace fails to loadAleksey Kladov2019-03-051-1/+2
|
* Add optional range parameter to SyntaxTreeParamsVille Penttinen2019-03-031-0/+1
| | | | | When range is provided, instead of showing the syntax for the whole file, we'll show the syntax tree for the given range.
* Go to Implementation for structs and enumsJeremy Kolb2019-01-301-1/+1
|
* align command namingAleksey Kladov2019-01-281-11/+11
|
* add gc requestAleksey Kladov2019-01-251-0/+8
|
* ad status commandAleksey Kladov2019-01-221-0/+8
|
* switch to lsp-typesAleksey Kladov2019-01-141-2/+2
|
* Code lens support for running testsJeremy A. Kolb2019-01-111-2/+2
|
* use lsp WorkspaceEdit instead of custom source_file_edits and file_system_editsBernardo2019-01-031-19/+3
|
* remove explicit serde_deriveAleksey Kladov2018-12-211-1/+1
|
* modernize moreAleksey Kladov2018-12-061-0/+1
|
* Fully add inline modules to module treeAleksey Kladov2018-11-051-1/+1
|
* Reformat allAleksey Kladov2018-10-311-2/+2
|
* Implement Find All References for local variablesJeremy A. Kolb2018-10-181-1/+1
|
* Cargo FormatJeremy A. Kolb2018-10-161-17/+10
| | | | Run `cargo fmt` and ignore generated files
* Language Server: textDocument/signatureHelpJeremy A. Kolb2018-10-111-0/+1
| | | | | | | | | | 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
* Replace HashMap, HashSet with FxHashMap and FxHashSetMuhammad Mominul Huque2018-10-111-2/+2
|
* Add on-enter handlerAleksey Kladov2018-10-091-0/+8
| | | | Now, typing doc comments is much more pleasant
* rename all thingsAleksey Kladov2018-09-161-0/+176