mirror of
https://github.com/zed-industries/zed.git
synced 2024-09-16 00:47:39 +03:00
bac6e2fee7
Context: @bennetbo spotted a regression in handling of `cargo run` task in zed repo following a merge of #13658. We've started invoking `cargo run` from the folder of an active file whereas previously we did it from the workspace root. We brainstormed few solutions that involved adding a separate task that gets invoked at a workspace level, but I realized that a cleaner solution may be to finally add user-configured task variables. This way, we can choose which crate to run by default at a workspace level. This has been originally brought up in the context of javascript tasks in https://github.com/zed-industries/zed/pull/12118#issuecomment-2129232114 Note that this is intended for internal use only for the time being. /cc @RemcoSmitsDev we should be unblocked on having runner-dependant tasks now. Release notes: - N/A
35 lines
636 B
JSON
35 lines
636 B
JSON
{
|
|
"languages": {
|
|
"Markdown": {
|
|
"tab_size": 2,
|
|
"formatter": "prettier"
|
|
},
|
|
"TOML": {
|
|
"formatter": "prettier",
|
|
"format_on_save": "off"
|
|
},
|
|
"YAML": {
|
|
"tab_size": 2,
|
|
"formatter": "prettier"
|
|
},
|
|
"JSON": {
|
|
"tab_size": 2,
|
|
"formatter": "prettier"
|
|
},
|
|
"JavaScript": {
|
|
"tab_size": 2,
|
|
"formatter": "prettier"
|
|
},
|
|
"Rust": {
|
|
"tasks": {
|
|
"variables": {
|
|
"RUST_DEFAULT_PACKAGE_RUN": "zed"
|
|
}
|
|
}
|
|
}
|
|
},
|
|
"formatter": "auto",
|
|
"remove_trailing_whitespace_on_save": true,
|
|
"ensure_final_newline_on_save": true
|
|
}
|