aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src
Commit message (Collapse)AuthorAgeFilesLines
...
* Add `inRustProject` when-clause for commands.vsrs2020-05-272-0/+11
|
* Partially fix displaying inlay hints in Github PR diff viewsveetaha2020-05-261-4/+5
|
* Document `parentModule` experimental LSP requestAleksey Kladov2020-05-252-4/+4
|
* Cleanup lsp extensions on the client sideAleksey Kladov2020-05-256-127/+88
|
* Less rust-analyzer specific onEnterAleksey Kladov2020-05-253-7/+9
|
* Flatten commands.tsAleksey Kladov2020-05-254-109/+103
|
* Flatten simple commandsAleksey Kladov2020-05-2510-301/+242
|
* Remove dead codeAleksey Kladov2020-05-254-106/+54
|
* Introduce `toggle inlay hints` vscode commandveetaha2020-05-254-1/+14
| | | | | | | | Users now can assign a shortcut for this command via the general vscode keybindings ui or `keybinding.json file` Closes: #4599
* Document matchingBrace LSP requestAleksey Kladov2020-05-242-6/+5
|
* Merge pull request #4538 from vsrs/vscode_testsAleksey Kladov2020-05-231-23/+34
|\ | | | | vscode client side tests
| * Apply suggestions from @Veetaha code reviewvsrs2020-05-211-10/+4
| |
| * vscode client side testsvsrs2020-05-201-23/+40
| |
* | 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
| |
* | 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
* 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
|
* Add "rust-analyzer.lens.enable"vsrs2020-05-181-0/+2
|
* code formattingvsrs2020-05-171-1/+1
|
* Runnable QuickPick with debuggees onlyvsrs2020-05-171-3/+14
|
* CodeLens configuration options.vsrs2020-05-171-0/+11
|
* Merge #4448bors[bot]2020-05-155-100/+244
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-142-14/+10
| |
| * Use launch.json in Debug Lens sessions.vsrs2020-05-132-2/+20
| | | | | | | | 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-113-3/+31
| |
| * "rust-analyzer.debug" commandvsrs2020-05-113-106/+139
| |
* | Make some stuff public so that they can be reused by other toolsPavan Kumar Sunkara2020-05-141-1/+1
| |
* | Merge #4083bors[bot]2020-05-131-1/+1
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | 4083: Smol documentation for ast nodes r=matklad a=Veetaha There is a tremendous amount of TODOs to clarify the topics I am not certain about. Please @matklad, @edwin0cheng review carefully, I even left some mentions of your names in todos to put your attention where you most probably can give comments. In order to simplify the review, I separated the codegen (i.e. changes in `ast/generated/nodes.rs`) from `ast_src` changes (they in fact just duplicate one another) into two commits. Also, I had to hack a little bit to let the docs be generated as doc comments and not as doc attributes because it's easier to read them this way and IIRC we don't support hints for `#[doc = ""]` attributes for now... Closes #3682 Co-authored-by: veetaha <[email protected]>
| * Fix "show syntax tree" commandveetaha2020-05-101-1/+1
| | | | | | | | @matlkad please don't forget to keep it up-to-date!
* | Word fixEdwin Cheng2020-05-101-1/+1
|/