Input variables only work with one configuration in a compound launch config

[matbarker]

• VSCode Version: VSCode 1.30.2
• OS Version: Windows 10 Pro

Steps to reproduce

1. Create a launch.json that has two configs, each referencing an input variable
2. Create a compound using both of those two configs
3. Launch the compound task.

Expected: User is prompted to select input variable, input variable is passed to all configs in the compound and all tasks in the compound are run.

Actual: User is prompted to select input variable, only the last config in the compound is run.

Example launch.json:

{
            "type": "node",
            "request": "launch",
            "name": "Launch Program",
            "program": "${workspaceFolder}/hey.js",
            "env": {
                "Test": "${input:componentType}"
            }
        },
        {
            "type": "node",
            "request": "launch",
            "name": "Launch Program2",
            "program": "${workspaceFolder}/hey2.js",
            "env": {
                "Test": "${input:componentType}"
            }
        }
    ,],
    "compounds": [
        {
            "name": "Compound",
            "configurations": ["Launch Program", "Launch Program2"]
        }
    ],
    "inputs": [
        {
            "id": "componentType",
            "description": "What type of component do you want to create?",
            "default": "component",
            "type": "pickString",
            "options": ["component", "directive"]
        }
    ]
}

hey.js/hey2.js:

debugger;
console.log('foo');

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• Allow preLaunch task for compound list (#45676)

[weinand]

If one launch config of a compound contains an "input variable", the succeeding launch configs are not started.

So if the "input variable" is only used in the last launch config, all launch configs are started.