aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src
Commit message (Collapse)AuthorAgeFilesLines
* Migrate flycheck to fully-lsp-compatible progress reports (introduce ↵veetaha2020-06-182-103/+0
| | | | ra_progress crate)
* Fix Run lens.vsrs2020-06-061-1/+1
|
* Remove hover contents marking as trusted.vsrs2020-06-051-15/+2
| | | | | Hover contents might be extracted from raw doc comments and need some validation.
* Add hover actions LSP extension documentation.vsrs2020-06-051-1/+1
|
* Add hover actions as LSP extensionvsrs2020-06-053-4/+66
|
* Fix review commentsMikhail Rakhmanov2020-06-032-3/+0
|
* Merge remote-tracking branch 'upstream/master' into compute-lazy-assitsMikhail Rakhmanov2020-06-023-21/+29
|\ | | | | | | | | # Conflicts: # crates/rust-analyzer/src/to_proto.rs
| * Spec better runnablesAleksey Kladov2020-06-021-1/+1
| |
| * New runnables APIAleksey Kladov2020-06-023-20/+28
| |
* | Preliminary implementation of lazy CodeAssitsMikhail Rakhmanov2020-06-024-38/+65
|/
* Move run commands to commands.tsAleksey Kladov2020-06-023-133/+134
|
* Merge #4580bors[bot]2020-06-026-52/+100
|\ | | | | | | | | | | | | | | | | | | | | | | 4580: Fix invoking cargo without consulting CARGO env var or standard installation paths r=matklad a=Veetaha Followup for #4329 The pr essentially fixes [this bug](https://youtu.be/EzQ7YIIo1rY?t=2189) cc @lefticus Co-authored-by: veetaha <[email protected]>
| * Change Runnable.bin -> Runnable.kindveetaha2020-05-316-52/+97
| | | | | | | | | | | | As per matklad, we now pass the responsibility for finding the binary to the frontend. Also, added caching for finding the binary path to reduce the amount of filesystem interactions.
| * Fix invoking cargo without consulting CARGO or standard installation pathsveetaha2020-05-312-4/+7
| |
* | Always derive from `process.env` when spawning a child process/shell executionAlin Sinpalean2020-05-311-1/+1
|/ | | | | | | | | | This is useful when an extension (e.g. Nix Environment Selector) or launch configuration sets one or more environment variables. When `env` is not explicitly specified in the options passed to `child_process.spawn()` or `vscode.ShellExecution()`, then `process.env` gets applied automatically. But when an explicit `env` is set, it should inherit from `process.env` rather than replace it completely.
* 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
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-12 07:22:20 +0000