| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Support 'runnables' options in the vs code extension | Igor Aleksanov | 2020-10-02 | 1 | -0/+2 |
| | | |||||
| * | Fix workspaceRoot | vsrs | 2020-07-03 | 1 | -1/+3 |
| | | |||||
| * | code linting | vsrs | 2020-07-03 | 1 | -1/+1 |
| | | |||||
| * | Add tests | vsrs | 2020-07-03 | 1 | -7/+7 |
| | | |||||
| * | Add runnable env support. | vsrs | 2020-07-03 | 1 | -5/+24 |
| | | |||||
| * | Add light-weight snapshot testing library with editor integration | Aleksey Kladov | 2020-06-27 | 1 | -1/+5 |
| | | |||||
| * | Switch to ShellExecution instead of full Task | vsrs | 2020-06-24 | 1 | -1/+2 |
| | | |||||
| * | Add custom cargo runners | vsrs | 2020-06-24 | 1 | -40/+17 |
| | | |||||
| * | Fix Run lens. | vsrs | 2020-06-06 | 1 | -1/+1 |
| | | |||||
| * | New runnables API | Aleksey Kladov | 2020-06-02 | 1 | -6/+15 |
| | | |||||
| * | Move run commands to commands.ts | Aleksey Kladov | 2020-06-02 | 1 | -71/+3 |
| | | |||||
| * | Merge #4580 | bors[bot] | 2020-06-02 | 1 | -1/+2 |
| |\ | | | | | | | | | | | | | | | | | | | | | | | 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.kind | veetaha | 2020-05-31 | 1 | -1/+2 |
| | | | | | | | | | | | | | 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. | ||||
| * | | Always derive from `process.env` when spawning a child process/shell execution | Alin Sinpalean | 2020-05-31 | 1 | -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. | ||||
| * | Cleanup lsp extensions on the client side | Aleksey Kladov | 2020-05-25 | 1 | -1/+1 |
| | | |||||
| * | Flatten commands.ts | Aleksey Kladov | 2020-05-25 | 1 | -0/+204 |
 |
index : rust-analyzer | |
| [FORK] modified to work on wasm targets |
| aboutsummaryrefslogtreecommitdiff |