Support to pass arguments to command-based variables

[weinand]

For launch.json and task.json configuration files VS Code supports variables that are based on commands. One limitation of this mechanism is that it is not possible to pass additional arguments to the command.

Examples:

• C# auto attach to process #32726: asks for being able to pass a filter pattern to the process picker command, e.g. something like ${command:autoPickProcessWithPattern:TopTen-Server.dll}
• Feature Request: "enum" launch config variable #9297: asks for a command that uses QuickPick to select from a list of enums, e.g. something like ${command:enumQuickPick:'choice 1','choice 2', 'choice 3'}"

[bitjson]

I'm hoping to implement #50758 as an extension – any news on this feature request?

[isidorn]

@weinand should we close this?

[bitjson]

@isidorn is this functionality available somehow? I'd love to be able to provide a parameter to a contributed command (for use in launch.json).

It doesn't seem like there's even a good hack to make that happen though – even if I parse the configuration to consume the parameter in a different way, the user is shown an error on unrecognized configuration options. So the only way to provide information to a command is by somehow embedding it in existing configuration options.

[RobertDeRose]

Would love for this feature to be supported

[weinand]

Next week we will support passing arguments to command based variables via #64362:

{
	"version": "0.2.0",
	"configurations": [
		{
			"type": "node",
			"request": "launch",
			"name": "Launch Program",
			"program": "${input:askForXYZ}"
		}
	],
	"inputs": [
		{
			"id": "askForXYZ",
			"type": "command",
			"description": "The XYZ to use"
			"command": "extension.foobar.someCommand",
		}
	]
}

[busticated]

@weinand will this also be supported via TaskProvider? (docs)

[weinand]

I don't understand your question but "input" variables (like the example from above) will be supported in task.json too.

[busticated]

I don't understand your question

if i'm providing tasks configuration via vscode.workspace.registerTaskProvider() (and related), will i be able to use "input" variables?

[weinand]

Are you able to use other variables, e.g. ${workspaceFolder} or ${env:HOME}?
If the answer is yes, then you are able to use "input" variables as well.

Sorry, I cannot give you a better answer because this issue is "debug" related, and I'm not an expert on "tasks".

[weinand]

this feature has become available via #64362.