Test resolved variables for custom execution tasks

[alexr00]

Refs: #81007

• macOS @chrmarti
• linux @jrieken
• windows @eamodio

Complexity: 4

Create Issue

---

You can start from the custom execution task sample. The callback you need to modify is here:
https://github.com/microsoft/vscode-extension-samples/blob/aa174fe79657d9b69cdb6cd2c6306c50c49b512d/task-provider-sample/src/customTaskProvider.ts#L73

Variables in custom execution tasks are now resolved and passed back to the task callback:

vscode/src/vs/vscode.d.ts

Line 6134 in 57e9e1a

constructor(callback: (resolvedDefinition: TaskDefinition) => Thenable<Pseudoterminal>);

To verify, you'll need to change the callback in the custom execution task sample to use the parameter in the API. Verify that if there are variables in the tasks.json file for a custombuildscript task that they are resolved and passed into the task callback when the task is run. All variables should be resolved (standard ones, input, and command). Variable docs. If a variable is used twice in the task and it requires input, it should only be prompted for once. Example of a custombuildscript task in tasks.json with some variables:

		{
			"type": "custombuildscript",
			"flavor": "${input:chooseNumber}",
			"flags": ["${workspaceFolder}"],
			"problemMatcher": [],
			"label": "custombuildscript: 64 "
		}