diff options
| author | bors <bors@rust-lang.org> | 2024-04-01 10:17:07 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-04-01 10:17:07 +0000 |
| commit | f3f14d4552edf440bf1a1cfe44788fcfd11949ea (patch) | |
| tree | 96f181ad66a9aef323e8914257da608f439d613d /tests/ui/patchable-function-entry/patchable-function-entry-flags.rs | |
| parent | 9774b114c67d71853713850e2fd220e2f31d971e (diff) | |
| parent | a758e349bca3eb3ab8b775c51bd8c797869395b9 (diff) | |
| download | rust-f3f14d4552edf440bf1a1cfe44788fcfd11949ea.tar.gz rust-f3f14d4552edf440bf1a1cfe44788fcfd11949ea.zip | |
Auto merge of #16970 - Wilfred:fix_tasks, r=Veykril
Fix tasks in tasks.json
#16839 refactored the representation of tasks inside the VS Code extension. However, this data type is exposed to users, who can define their own tasks in the same format in `tasks.json` or `.code-workspace`.
Revert the data type to have a `command` field rather than a `program` field, and document the different fields. This code is also a little complex, so split out a `cargoToExecution` to handle the Task to Execution conversion logic.
After this change, any tasks.json with a `command` field works again. For example, the following tasks.json works as expected:
```
{
"version": "2.0.0",
"tasks": [
{
"type": "cargo",
"command": "build",
"problemMatcher": [
"$rustc"
],
"group": "build",
"label": "my example cargo build task"
}
]
}
```
Fixes #16943 #16949
Diffstat (limited to 'tests/ui/patchable-function-entry/patchable-function-entry-flags.rs')
0 files changed, 0 insertions, 0 deletions
