aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src
Commit message (Collapse)AuthorAgeFilesLines
...
* 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
|/
* Merge remote-tracking branch 'upstream/master' into uniformed_debug_lensvsrs2020-05-085-45/+70
|\ | | | | | | | | # Conflicts: # editors/code/src/commands/runnables.ts
| * Merge #4329bors[bot]2020-05-084-40/+67
| |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4329: Look for `cargo`, `rustc`, and `rustup` in standard installation path r=matklad a=cdisselkoen Discussed in #3118. This is approximately a 90% fix for the issue described there. This PR creates a new crate `ra_env` with a function `get_path_for_executable()`; see docs there. `get_path_for_executable()` improves and generalizes the function `cargo_binary()` which was previously duplicated in the `ra_project_model` and `ra_flycheck` crates. (Both of those crates now depend on the new `ra_env` crate.) The new function checks (e.g.) `$CARGO` and `$PATH`, but also falls back on `~/.cargo/bin` manually before erroring out. This should allow most users to not have to worry about setting the `$CARGO` or `$PATH` variables for VSCode, which can be difficult e.g. on macOS as discussed in #3118. I've attempted to replace all calls to `cargo`, `rustc`, and `rustup` in rust-analyzer with appropriate invocations of `get_path_for_executable()`; I don't think I've missed any in Rust code, but there is at least one invocation in TypeScript code which I haven't fixed. (I'm not sure whether it's affected by the same problem or not.) https://github.com/rust-analyzer/rust-analyzer/blob/a4778ddb7a00f552a8e653bbf56ae9fd69cfe1d3/editors/code/src/cargo.ts#L79 I'm sure this PR could be improved a bunch, so I'm happy to take feedback/suggestions on how to solve this problem better, or just bikeshedding variable/function/crate names etc. cc @Veetaha Fixes #3118. Co-authored-by: Craig Disselkoen <[email protected]> Co-authored-by: veetaha <[email protected]>
| | * Fix cargo not found on macos bug at vscode extension sideveetaha2020-05-063-7/+48
| | |
| | * Preliminary refactoring of cargo.tsveetaha2020-05-062-33/+19
| | |
| * | Add master config for inlayHints to make disabling easyAleksey Kladov2020-05-082-7/+8
| |/
* | Add CodeLLDB Rust visualizationvsrs2020-05-071-1/+2
| |
* | Add separate settings for each debug engine.vsrs2020-05-071-3/+6
| |
* | Add additional debug optionsvsrs2020-05-072-3/+11
| |
* | Uniformed way to get Debug Lens target executable.vsrs2020-05-062-28/+37
|/
* Drop dead code and a dependency!veetaha2020-05-051-129/+0
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-03 23:21:56 +0000