aboutsummaryrefslogtreecommitdiff
path: root/editors/code
Commit message (Collapse)AuthorAgeFilesLines
* Introduce `toggle inlay hints` vscode commandveetaha2020-05-255-1/+19
| | | | | | | | Users now can assign a shortcut for this command via the general vscode keybindings ui or `keybinding.json file` Closes: #4599
* Merge #4593bors[bot]2020-05-242-6/+5
|\ | | | | | | | | | | | | | | | | | | | | 4593: Document some rust-analyzer specific protocol extensions r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * Document matchingBrace LSP requestAleksey Kladov2020-05-242-6/+5
| |
* | Highlight `true` and `false` as literalsMatthew Jasper2020-05-241-0/+3
|/
* Merge pull request #4574 from lnicola/bump-depsAleksey Kladov2020-05-242-244/+342
|\ | | | | Bump some dependencies
| * Bump more npm depsLaurențiu Nicola2020-05-242-240/+338
| |
| * Bump some npm depsLaurențiu Nicola2020-05-242-39/+39
| |
* | Merge pull request #4474 from georgewfraser/color_attrsAleksey Kladov2020-05-242-1/+13
|\ \ | |/ |/| Color attribute functions
| * Color attribute functionsGeorge Fraser2020-05-192-1/+13
| |
* | Merge pull request #4538 from vsrs/vscode_testsAleksey Kladov2020-05-239-32/+956
|\ \ | | | | | | vscode client side tests
| * | Apply suggestions from @Veetaha code reviewvsrs2020-05-213-53/+44
| | |
| * | vscode client side testsvsrs2020-05-209-32/+965
| | |
* | | Merge #4555 #4575bors[bot]2020-05-231-1/+48
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4555: VSCode: added patchelf after download for NixOS support r=matklad a=cab404 This adds Nix support, and fixes #4542 4575: Use Chalk's built-in representations for fn items and pointers r=matklad a=flodiebold The `TypeName::FnDef` was just added; the function pointer variant has existed for a while, I just forgot about it because it's special (because fn pointers can be higher-ranked over lifetimes). We *could* also make `FnPtr` a separate `Ty` variant instead of a `TypeCtor` variant, which would make the conversion code a bit less special-casey, but it doesn't seem worth doing right now. Co-authored-by: Vladimir Serov <[email protected]> Co-authored-by: Cabia Rangris <[email protected]> Co-authored-by: Florian Diebold <[email protected]>
| * \ \ Merge branch 'nix-patchelf' of github.com:cab404/rust-analyzer into nix-patchelfVladimir Serov2020-05-211-1/+1
| |\ \ \
| | * | | Update editors/code/src/main.tsCabia Rangris2020-05-211-1/+1
| | | | | | | | | | | | | | | Co-authored-by: Jeremy Kolb <[email protected]>
| * | | | editors/vscode: forgotten await in os checkVladimir Serov2020-05-211-1/+1
| | | | |
| * | | | editors/vscode: patchelf-ing without intermediate filesVladimir Serov2020-05-211-5/+5
| |/ / /
| * | | editor/vscode: lintVladimir Serov2020-05-211-21/+21
| | | |
| * | | editors/vscode: removing original file after patchingVladimir Serov2020-05-211-1/+1
| | | |
| * | | editors/vscode: added patchelf after downloadVladimir Serov2020-05-211-1/+48
| |/ /
* | | CodeAction groupsAleksey Kladov2020-05-223-14/+43
| | |
* | | Use WorkspaceEdit for ssrAleksey Kladov2020-05-212-5/+3
| | |
* | | Formalize JoinLines protocol extensionAleksey Kladov2020-05-212-6/+10
| | |
* | | Merge #4552bors[bot]2020-05-214-31/+53
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4552: Transition OnEnter to WorkspaceSnippetEdit r=matklad a=matklad This also changes our handiling of snippet edits on the client side. `editor.insertSnippet` unfortunately forces indentation, which we really don't want to have to deal with. So, let's just implement our manual hacky way of dealing with a simple subset of snippets we actually use in rust-analyzer bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | Transition OnEnter to WorkspaceSnippetEditAleksey Kladov2020-05-214-31/+53
| |/ / | | | | | | | | | | | | | | | | | | | | | This also changes our handiling of snippet edits on the client side. `editor.insertSnippet` unfortunately forces indentation, which we really don't want to have to deal with. So, let's just implement our manual hacky way of dealing with a simple subset of snippets we actually use in rust-analyzer
* / / Fix phrasing in inlay hints settingsLaurențiu Nicola2020-05-211-4/+4
|/ /
* | Debug lens fix for a binary.vsrs2020-05-201-4/+8
| |
* | Fix client-side snippetsAleksey Kladov2020-05-191-1/+2
| |
* | Implement client-side of SnippetTextEditAleksey Kladov2020-05-193-2/+81
| |
* | Add snippetTextEdit protocol extensionAleksey Kladov2020-05-191-4/+15
|/
* Merge #4499bors[bot]2020-05-183-3/+47
|\ | | | | | | | | | | | | | | | | | | 4499: CodeLens configuration options r=vsrs a=vsrs This PR - adds an option to granularly enable\disable all CodeLens, just like the TypeScript extension. - fixes a minor bug for doctests. It makes no sense to show `Debug` lens for them as cargo `Can't skip running doc tests with --no-run`. Co-authored-by: vsrs <[email protected]>
| * Add "rust-analyzer.lens.enable"vsrs2020-05-182-3/+10
| |
| * code formattingvsrs2020-05-171-1/+1
| |
| * Runnable QuickPick with debuggees onlyvsrs2020-05-171-3/+14
| |
| * CodeLens configuration options.vsrs2020-05-172-0/+26
| |
* | Relax VS Code version requirementAleksey Kladov2020-05-171-2/+2
|/
* Color macros (fixes #4462)George Fraser2020-05-161-0/+3
|
* Merge #4448bors[bot]2020-05-156-100/+254
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4448: Generate configuration for launch.json r=vsrs a=vsrs This PR adds two new commands: `"rust-analyzer.debug"` and `"rust-analyzer.newDebugConfig"`. The former is a supplement to the existing `"rust-analyzer.run"` command and works the same way: asks for a runnable and starts new debug session. The latter allows adding a new configuration to **launch.json** (or to update an existing one). If the new option `"rust-analyzer.debug.useLaunchJson"` is set to true then `"rust-analyzer.debug"` and Debug Lens will first look for existing debug configuration in **launch.json**. That is, it has become possible to specify startup arguments, env variables, etc. `"rust-analyzer.debug.useLaunchJson"` is false by default, but it might be worth making true the default value. Personally I prefer true, but I'm not sure if it is good for all value. ---- I think that this PR also solves https://github.com/rust-analyzer/rust-analyzer/issues/3441. Both methods to update launch.json mentioned in the issue do not work: 1. Menu. It is only possible to add a launch.json configuration template via a debug adapter. And anyway it's only a template and it is impossible to specify arguments from an extension. 2. DebugConfigurationProvider. The exact opposite situation: it is possible to specify all debug session settings, but it is impossible to export these settings to launch.json. Separate `"rust-analyzer.newDebugConfig"` command looks better for me. ---- Fixes #4450 Fixes #3441 Co-authored-by: vsrs <[email protected]> Co-authored-by: vsrs <[email protected]>
| * Fix occasional test run during debug configurationvsrs2020-05-151-1/+5
| |
| * Fix runnable naming in the client side fallback.vsrs2020-05-141-1/+1
| |
| * Multiple binaries support for launch.json.vsrs2020-05-141-2/+3
| | | | | | | | Generate unique names on the LSP side.
| * Mixed "bin" and "test" artifacts workaround.vsrs2020-05-141-2/+7
| |
| * Multiple binaries support for launch.json.vsrs2020-05-141-0/+5
| |
| * Fix "rust-analyzer.debug" for QuickPick binaries.vsrs2020-05-141-0/+4
| |
| * Runnable quick pick with buttonsvsrs2020-05-141-21/+61
| |
| * Remove "rust-analyzer.debug.useLaunchJson" optionvsrs2020-05-143-19/+10
| |
| * Use launch.json in Debug Lens sessions.vsrs2020-05-133-2/+25
| | | | | | | | Add the possibility to use existing configurations via Debug Lens
| * DebugConfiguration simplification.vsrs2020-05-111-1/+11
| | | | | | | | ${workspaceRoot} substitution in generated DebugConfiguration.
| * "rust-analyzer.newDebugConfig" commandvsrs2020-05-114-3/+36
| |
| * "rust-analyzer.debug" commandvsrs2020-05-114-106/+144
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-27 02:16:27 +0000