| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2023-05-18 | fix: Force disable augmentsSyntaxTokens capability on VSCode | Lukas Wirth | -0/+20 | |
| 2023-04-09 | fix: Fix project linking popup appearing for modules that can be linked to a ↵ | Lukas Wirth | -1/+5 | |
| crate | ||||
| 2023-04-04 | fix: Fix relative path creation using the wrong path accessor | Lukas Wirth | -5/+9 | |
| 2023-04-04 | fix: Fix vscode project linking popup buttons being swapped | Lukas Wirth | -3/+4 | |
| 2023-03-25 | Fix lints | Lukas Wirth | -40/+35 | |
| 2023-03-16 | feat: Pop a notification prompting the user to add a Cargo.toml of unlinked ↵ | Lukas Wirth | -10/+64 | |
| file to the linkedProjects | ||||
| 2023-03-14 | fix: don't override `linkedProjects` if no workspace was discovered. | David Barsky | -1/+6 | |
| 2023-03-14 | Address review comments | David Barsky | -1/+3 | |
| 2023-03-13 | Remove `rust-analyzer/addProject` in favor of notifying r-a that ↵ | David Barsky | -1/+1 | |
| configuration has changed | ||||
| 2023-03-13 | Add a workspace config-based approach to reloading discovered projects. | David Barsky | -3/+5 | |
| 2023-01-23 | 🧹 lsp_ext.ts | Lukas Wirth | -22/+21 | |
| 2023-01-23 | Add a 'open server logs' button to the error notification | Lukas Wirth | -0/+1 | |
| 2023-01-10 | Revert "Use ZWNJ to prevent VSCode from forming ligatures between hints and ↵ | Lukas Wirth | -18/+0 | |
| code" | ||||
| 2023-01-09 | Use experimental capability to enable color codes | Ian Chamberlain | -0/+1 | |
| 2023-01-09 | Strip colors before matching preview diagnostics | Ian Chamberlain | -2/+4 | |
| 2023-01-09 | Parse + decorate rendered ANSI cargo output | Ian Chamberlain | -5/+6 | |
| Use ANSI control characters to display text decorations matching the VScode terminal theme, and strip them out when providing text content for rustc diagnostics. This adds the small `anser` library to parse the control codes, and it also supports HTML output so it should be fairly easy to switch to a rendered HTML/webview implementation if desired. | ||||
| 2023-01-03 | Use ZWNJ to prevent VSCode from forming ligatures between hints and code | Lukas Wirth | -0/+18 | |
| 2023-01-03 | Fix diagnostic code | Alex Veber | -2/+12 | |
| 2022-11-18 | feat: Allow viewing the full compiler diagnostic in a readonly textview | Lukas Wirth | -2/+40 | |
| 2022-10-17 | Implement stop and start server commands | Lukas Wirth | -0/+8 | |
| 2022-10-17 | Refactor language client handling | Lukas Wirth | -33/+10 | |
| 2022-10-16 | Substitute some VSCode variables in the VSCode client | Lukas Wirth | -4/+22 | |
| 2022-08-28 | Move empty diagnostics workaround back into the server | Lukas Wirth | -16/+0 | |
| 2022-08-22 | Remove auto-config patching from the VSCode client | Lukas Wirth | -6/+0 | |
| 2022-08-13 | Pad empty diagnostic messages in relatedInformation as well | Lukas Wirth | -0/+7 | |
| 2022-08-13 | Move VSCode diagnostics workaroudn into client code | Lukas Wirth | -0/+9 | |
| 2022-07-23 | Revert 03a62c180e6a7300d0d7b8c4d680b749c101bcbb | Lukas Wirth | -4/+0 | |
| 2022-07-09 | Bump vscode-languageclient | Laurențiu Nicola | -0/+4 | |
| 2022-06-05 | internal: Keep output channels across restarts | Lukas Wirth | -4/+3 | |
| 2022-05-18 | "Show implementations" link display error fix | Andrei Listochkin | -3/+35 | |
| While VSCode [uses it's own implementation for URIs](https://github.com/microsoft/vscode-uri) which notably doesn't have any limits of URI size, the renderer itself relies on Web platform engine, that limits the length of the URLs and bails out when the attribute length of an `href` inside `a` tag is too long. Command URIs have a form of `command:command-name?arguments`, where `arguments` is a percent-encoded array of data we want to pass along to the command function. For "Show References" this is a list of all file URIs with locations of every reference, and it can get quite long. This PR introduces another intermediary `linkToCommand` command. When we render a command link, a reference to a command with all its arguments is stored in a map, and instead a `linkToCommand` link is rendered with the key to that map. For now the map is cleaned up periodically (I've set it to every 10 minutes). In general case we'll probably need to introduce TTLs or flags to denote ephemeral links (like these in hover popups) and persistent links and clean those separately. But for now simply keeping the last few links in the map should be good enough. Likewise, we could add code to remove a target command from the map after the link is clicked, but assuming most links in hover sheets won't be clicked anyway this code won't change the overall memory use much. Closes #9926 | ||||
| 2022-05-17 | prettier run | Andrei Listochkin | -112/+165 | |
| 2022-05-13 | Don't make r-a fail to initialize if updating the config fails | Lukas Wirth | -1/+3 | |
| 2022-05-11 | Enable variable substitutions before passing them over to R-A server | Andrei Listochkin | -3/+4 | |
| 2022-05-01 | auto update old configurations to newer ones | Lukas Wirth | -1/+6 | |
| 2022-04-08 | Update for languageclient API changes | Laurențiu Nicola | -3/+3 | |
| 2022-01-27 | Support <code> blocks from Rust docs | Andrew Onyshchuk | -0/+3 | |
| 2021-07-30 | feat: gate custom clint-side commands behind capabilities | Aleksey Kladov | -0/+9 | |
| 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 | lint: Format the typescript files properly | Alexander Gonzalez | -13/+13 | |
| 2021-07-27 | refactor: Make handle_hover handle ranges too | Alexander Gonzalez | -39/+5 | |
| 2021-07-27 | feat: Completed the client side implementation of rust-analyzer/hoverRange | Alexander Gonzalez | -11/+57 | |
| 2021-05-26 | Create tasks for all workspaces | Kirill Bulatov | -6/+1 | |
| 2021-05-23 | Fix ts lint errors | Kirill Bulatov | -2/+2 | |
| 2021-05-23 | Send detached files info to server via init params | Kirill Bulatov | -2/+13 | |
| 2021-05-23 | Start rust-analyzer server for arbitrary rust files | Kirill Bulatov | -1/+1 | |
| 2021-04-06 | More robust status notifications | Aleksey Kladov | -1/+1 | |
| 2021-02-16 | Remove Semantic Tokens flicker workaround | kjeremy | -17/+0 | |
| https://github.com/microsoft/vscode-languageserver-node/issues/576 has been closed with the latest vscode-languageclient release. | ||||
| 2021-02-14 | Start LSP 3.17 support | Jeremy Kolb | -1/+1 | |
| 2021-02-07 | fix errors | Sahandevs | -1/+1 | |
| 2021-02-07 | handle promise catches | Sahandevs | -1/+1 | |
| 2021-02-07 | remove unnecessary | Sahandevs | -1/+1 | |
 |
index : rust | |
| https://github.com/rust-lang/rust |
| about summary refs log tree commit diff |