| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2022-05-22 | internal: Allow OnTypeFormatting to send SnippetTextEdit | Felicián Németh | -2/+15 | |
| But continue to send TextEdit only. | ||||
| 2022-05-17 | Allow inlay hint tooltips to trigger hovers | Lukas Wirth | -1/+2 | |
| 2022-05-17 | Trigger hover requests on closing brace hints | Lukas Wirth | -0/+5 | |
| 2022-04-19 | Allows triggering commands after an assist edit | Jonas Schievink | -3/+2 | |
| 2022-04-08 | Switch to LSP inlay hints | Laurențiu Nicola | -46/+0 | |
| 2022-03-31 | Add "view file text" command to debug sync issues | Jonas Schievink | -0/+8 | |
| 2022-03-12 | minor: add missing definitions of lsp_ext::InlayHintLabel | Lukas Wirth | -1/+19 | |
| 2022-03-07 | Update LSP docs | Laurențiu Nicola | -1/+1 | |
| 2022-03-04 | Load hints for part of the file only | Kirill Bulatov | -0/+1 | |
| 2022-03-04 | Fixes | Laurențiu Nicola | -1/+0 | |
| 2022-03-04 | Update inlay hints for upstream | Laurențiu Nicola | -11/+15 | |
| 2022-03-04 | Add experimental VSCode api | Kirill Bulatov | -5/+8 | |
| 2022-02-07 | add missing snake case attribute, update hash | Moritz Vetter | -0/+1 | |
| 2021-12-07 | internal: add "Shuffle Crate Graph" command | Jonas Schievink | -0/+8 | |
| 2021-10-04 | Make multiple import edits work for completions | Lukas Wirth | -0/+5 | |
| 2021-07-30 | feat: gate custom clint-side commands behind capabilities | Aleksey Kladov | -0/+5 | |
| Some features of rust-analyzer requires support for custom commands on the client side. Specifically, hover & code lens need this. Stock LSP doesn't have a way for the server to know which client-side commands are available. For that reason, we historically were just sending the commands, not worrying whether the client supports then or not. That's not really great though, so in this PR we add infrastructure for the client to explicitly opt-into custom commands, via `extensions` field of the ClientCapabilities. To preserve backwards compatability, if the client doesn't set the field, we assume that it does support all custom commands. In the future, we'll start treating that case as if the client doesn't support commands. So, if you maintain a rust-analyzer client and implement `rust-analyzer/runSingle` and such, please also advertise this via a capability. | ||||
| 2021-07-27 | refactor: Make handle_hover handle ranges too | Alexander Gonzalez | -11/+13 | |
| 2021-07-27 | feat: Completed the client side implementation of rust-analyzer/hoverRange | Alexander Gonzalez | -2/+10 | |
| 2021-07-27 | feat: Extend the server with the hover_range capability | Alexander Gonzalez | -1/+8 | |
| 2021-07-04 | internal: better factoring for to_proto::completion | Aleksey Kladov | -0/+7 | |
| One source completion can produce up to two lsp completions. Additionally, `preselct` and `sort_text` are global properties of the whole set of completions, so the right granularity here is to convert many completions. As a side-benefit, we no loger allocate intermediate vec. | ||||
| 2021-07-02 | Add "View Crate Graph (Full)" | Jonas Schievink | -1/+8 | |
| 2021-05-21 | Add a "Debug ItemTree" LSP request | Jonas Schievink | -0/+14 | |
| 2021-05-18 | Add new LSP extension for workspace symbol lookup | alcroito | -1/+41 | |
| The new extension allows filtering of workspace symbool lookup results by search scope or search kind. Filtering can be configured in 3 different ways: - The '#' or '*' markers can be added inline with the symbol lookup query. The '#' marker means symbols should be looked up in the current workspace and any dependencies. If not specified, only current workspace is considered. The '*' marker means all kinds of symbols should be looked up (types, functions, etc). If not specified, only type symbols are returned. - Each LSP request can take an optional search_scope or search_kind argument query parameter. - Finally there are 2 global config options that can be set for all requests served by the active RA instance. Add support for setting the global config options to the VSCode extension. The extension does not use the per-request way, but it's useful for other IDEs. The latest version of VSCode filters out the inline markers, so currently the only reasonable way to use the new functionality is via the global config. | ||||
| 2021-05-11 | Allow viewing the crate graph in a webview | Jonas Schievink | -0/+8 | |
| 2021-04-18 | Prevent being able to rename items that are not part of the workspace | Lukas Wirth | -0/+6 | |
| 2021-04-14 | Move cursor position when using item movers | Jonas Schievink | -1/+1 | |
| 2021-04-06 | More robust status notifications | Aleksey Kladov | -15/+15 | |
| 2021-03-18 | Item up and down movers | ivan770 | -0/+22 | |
| 2021-03-11 | Apply review suggestions | vsrs | -8/+1 | |
| 2021-02-27 | Add LSP request and VSCode command | vsrs | -0/+20 | |
| 2021-02-16 | Enable offset-encoding capability | Aleksey Kladov | -0/+4 | |
| 2021-02-13 | Moved CodeLens to ide crate | ivan770 | -0/+8 | |
| 2021-02-12 | fix nightly warning `legacy_derive_helpers` | Peter Wischer | -1/+1 | |
| see https://github.com/rust-lang/rust/issues/79202 | ||||
| 2021-01-29 | Async Loading outdir and proc-macro | Edwin Cheng | -0/+1 | |
| 2020-12-28 | Initial implementation of view-hir command | Phil Ellison | -0/+8 | |
| 2020-11-16 | Latest LSP 3.16 protocol | kjeremy | -1/+1 | |
| Pulls in https://github.com/gluon-lang/lsp-types/pull/186 | ||||
| 2020-11-12 | add open Cargo.toml action | Anatol Liu | -0/+14 | |
| 2020-11-10 | Switch to upstream protocol for resolving code action | Aleksey Kladov | -18/+17 | |
| Note that we have to maintain custom implementation on the client side: I don't see how to marry bulitin resolve support with groups and snippets. | ||||
| 2020-10-08 | Changes from review | Zac Pullar-Strecker | -25/+5 | |
| 2020-10-08 | WIP: Command to open docs under cursor | Zac Pullar-Strecker | -0/+28 | |
| 2020-10-02 | Replace 'cargo_prefix' option with 'override_cargo' | Igor Aleksanov | -2/+2 | |
| 2020-10-02 | Add support of runnables arguments in Rust Analyzer | Igor Aleksanov | -0/+4 | |
| 2020-09-29 | Extend **Status** command to also show dep info for the file | Aleksey Kladov | -1/+7 | |
| This should help with troubleshooting wrong project configuration | ||||
| 2020-08-17 | Fix StatusNotification | vsrs | -1/+6 | |
| 2020-07-29 | SSR: Restrict to current selection if any | David Lattimore | -0/+3 | |
| The selection is also used to avoid unnecessary work, but only to the file level. Further restricting unnecessary work is left for later. | ||||
| 2020-07-24 | SSR: Pass current file position through to SSR code. | David Lattimore | -0/+5 | |
| In a subsequent commit, it will be used for resolving paths. | ||||
| 2020-07-16 | Mark machine applicable fixes as preferred | Jeremy Kolb | -0/+3 | |
| This allows us to run the auto fix command from vscode to automatically fix all diagnostics in the file. They are also distinguished in the UI. | ||||
| 2020-07-11 | Update lsp-types to account for new CodeActionKind structure | Jeremy Kolb | -2/+4 | |
| 2020-07-11 | Make sure there are no commands in code actions | Aleksey Kladov | -2/+3 | |
| 2020-07-07 | Add a command to compute memory usage statistics | Jonas Schievink | -0/+8 | |
