Multi-root: support Compound debug configurations across workspace folders

[auchenberg]

With multi-root its quite common to have back-end and front-end projects as separate folders loaded in the same workspace. Today a compound defined in one workspace folder doesn't seem to be able to reference another workspace debug config

We should enable compound debug configurations to work across workspaces, to enable a full-stack debug experience. We already provide a aggregated debug config list in the Debug UI.

[isidorn]

I think this feature request makes perfect sense. But I would wait a bit for users to pick up multi root workspaces and see if users jump on this feature before doing anything here.

[weinand]

@auchenberg in your initial comment you said

Today a compound defined in one workspace folder doesn't seem to be able to reference another workspace debug config.

I assume that you've meant:

Today a compound defined in one workspace folder doesn't seem to be able to reference another debug config in a different folder of the same workspace.

I've changed the title of this issue to reflect this.

[weinand]

We have to decide whether a compound launch config spanning different folders is only allowed in a workspace launch config or in individual folder launch configs. The former case is covered by feature request: #36967

[auchenberg]

You could make the argument that a workspace compound should be within <workspace>/.vscode/launch.json in order to be able to reference a specific launch config within a workspace folder.

[Disane87]

Is there an estimated release date for this?