aboutsummaryrefslogtreecommitdiff
path: root/editors/code/package.json
Commit message (Collapse)AuthorAgeFilesLines
* Add toggle for experimental diagnosticsJonas Schievink2020-07-241-5/+10
|
* ProblemMatcher auto detects relative/absolute paths and matches VSCode LSP's ↵James Leitch2020-07-231-3/+9
| | | | owner and source. VSCode LSP updated to specify owner.
* Automatically reload project info on Cargo.toml changesAleksey Kladov2020-07-101-0/+5
|
* Add a command to compute memory usage statisticsJonas Schievink2020-07-071-0/+10
|
* Merge #5203bors[bot]2020-07-031-1/+1
|\ | | | | | | | | | | | | | | 5203: Fix typo in description of vscode setting r=matklad a=Nashenas88 Co-authored-by: Paul Daniel Faria <[email protected]>
| * Fix typo in description of vscode settingPaul Daniel Faria2020-07-031-1/+1
| |
* | Add runnable env support.vsrs2020-07-031-0/+29
|/
* Add reload workspace commandAleksey Kladov2020-07-011-4/+4
|
* Be more strict with `@types/node`Laurențiu Nicola2020-07-011-1/+1
| | | | Co-authored-by: Veetaha <[email protected]>
* Use newer @types/nodeLaurențiu Nicola2020-06-291-1/+1
|
* Downgrade @types/nodeLaurențiu Nicola2020-06-281-1/+1
|
* Bump @rollup/plugin-commonjsLaurențiu Nicola2020-06-271-1/+1
|
* Bump some npm depsLaurențiu Nicola2020-06-271-10/+10
|
* Add custom cargo runnersvsrs2020-06-241-0/+8
|
* Disrecommend trace.server: "verbose" for regular usersVeetaha2020-06-221-1/+1
|
* Add `rust-analyzer.gotoLocation` commandvsrs2020-06-181-0/+5
|
* Warnings as hint or infoGabriel Valfridsson2020-06-161-0/+18
|
* checkOnSafe.features and checkOnSafe.allFeatures now work identically.Clemens Wasser2020-06-101-2/+5
|
* Most of the checkOnSafe options now default to the cargo equivalent.Clemens Wasser2020-06-101-4/+7
|
* Added the rust-analyzer.checkOnSave.features option.Clemens Wasser2020-06-101-0/+8
|
* Merge #4773bors[bot]2020-06-081-0/+10
|\ | | | | | | | | | | | | | | | | | | 4773: Run|Debug hover actions. r=matklad a=vsrs ![hover_actions_run](https://user-images.githubusercontent.com/62505555/83335644-dfc1f780-a2b6-11ea-820b-ccaa82290e7d.gif) This hover actions work exactly like corresponding lenses. Co-authored-by: vsrs <[email protected]>
| * Add Run|Debug hover actionsvsrs2020-06-061-0/+10
| |
* | Fix VSCode settingsVincent Isambart2020-06-071-4/+1
|/
* Add hover actions as LSP extensionvsrs2020-06-051-3/+13
|
* Document rust-project.jsonAleksey Kladov2020-06-031-0/+19
|
* Disable rust-analyzer.{cargo,checkOnSave}.allFeatures by defaultLaurențiu Nicola2020-06-021-2/+2
|
* Add `inRustProject` when-clause for commands.vsrs2020-05-271-1/+65
|
*-. Merge #4602 #4603bors[bot]2020-05-251-0/+10
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4602: Add boolean literal semantic token type to package.json r=matklad a=lnicola Closes #4583. CC @GrayJack 4603: Add self keyword semantic token type r=matklad a=lnicola Not sure if this is warranted a new token type or just a modifier. --- CC #4583, @GrayJack Co-authored-by: Laurențiu Nicola <[email protected]>
| | * Add self keyword semantic token typeLaurențiu Nicola2020-05-251-0/+5
| |/ |/|
| * Add boolean literals to package.jsonLaurențiu Nicola2020-05-251-0/+5
|/
* Introduce `toggle inlay hints` vscode commandveetaha2020-05-251-0/+5
| | | | | | | | Users now can assign a shortcut for this command via the general vscode keybindings ui or `keybinding.json file` Closes: #4599
* Highlight `true` and `false` as literalsMatthew Jasper2020-05-241-0/+3
|
* Merge pull request #4574 from lnicola/bump-depsAleksey Kladov2020-05-241-11/+11
|\ | | | | Bump some dependencies
| * Bump more npm depsLaurențiu Nicola2020-05-241-7/+7
| |
| * Bump some npm depsLaurențiu Nicola2020-05-241-8/+8
| |
* | Merge pull request #4474 from georgewfraser/color_attrsAleksey Kladov2020-05-241-0/+7
|\ \ | |/ |/| Color attribute functions
| * Color attribute functionsGeorge Fraser2020-05-191-0/+7
| |
* | Merge pull request #4538 from vsrs/vscode_testsAleksey Kladov2020-05-231-4/+11
|\ \ | | | | | | vscode client side tests
| * | vscode client side testsvsrs2020-05-201-4/+11
| |/
* / Fix phrasing in inlay hints settingsLaurențiu Nicola2020-05-211-4/+4
|/
* Merge #4499bors[bot]2020-05-181-0/+20
|\ | | | | | | | | | | | | | | | | | | 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-181-3/+8
| |
| * CodeLens configuration options.vsrs2020-05-171-0/+15
| |
* | 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-151-0/+10
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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]>
| * Remove "rust-analyzer.debug.useLaunchJson" optionvsrs2020-05-141-5/+0
| |
| * Use launch.json in Debug Lens sessions.vsrs2020-05-131-0/+5
| | | | | | | | Add the possibility to use existing configurations via Debug Lens
| * "rust-analyzer.newDebugConfig" commandvsrs2020-05-111-0/+5
| |
| * "rust-analyzer.debug" commandvsrs2020-05-111-0/+5
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-02 21:27:02 +0000