Piotr Osiewicz bac6e2fee7 tasks: Add experimental support for user-defined task variables (#13699) ... 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		2024-07-01 15:59:19 +02:00
..
default.json	tasks: Add experimental support for user-defined task variables (#13699)	2024-07-01 15:59:19 +02:00
initial_local_settings.json	Remove links to docs.zed.dev (#7187)	2024-01-31 22:26:15 -07:00
initial_tasks.json	Small improvements of the task terminal spawn behavior (#9399)	2024-03-15 18:32:59 +02:00
initial_user_settings.json	Default theme to match system (#13621)	2024-06-27 22:06:22 -06:00