multi debug: productise 'composite' launch config

[weinand]

TBD

related issues:
#14335
#14481
#14486

[isidorn]

I think we should also consider putting 'composites' as an additional section as a sibling to 'configurations' in launch.json. Since doing it the current way we might hit some limitations because required fields for configuraitons are not required for composites and in essence they are different.

I do not plan to work on composites this week so we can also discuss on Monday once I am back in Zh :)

[weinand]

In a ZRH team discussion concerns were raised that 'composite' launch configs have too much overlap with 'tasks' or 'scripts' and that debug should not open the door for this. So we decided not to release our existing implementation but to wait for task support for this.

So this feature is blocked now.

/cc @kieferrm @egamma @dbaeumer

[dbaeumer]

I think task is not the right place to solve this either. I do have similar requests. To make this scripting approach work I think we need the following :

• a scripting interface to VS Code (I have these requests in tasks since people want to talk back to VS Code from their tasks)
• if we want to use the OS scripts engines we need to have executables to talk to VS Code
• we could also say scripting happens in JS. Then we would provide a node module which we automatically inject into the started node engine to allow a script to talk back to VS Code.