Support for nested .vscode directories

[cjgatto]

A configuration in the active workspace should allow you to inherit from nested .vscode/ directories, so that inherited tasks.json, launch.json, etc. for child folders are usable from the opened workspace. This setting should allow you to specify which nested workspaces to include.

For example, a new .vscode/workspaces.json could hold this configuration:

{
  "my-company-*",
  "third-party-one/.vscode",
  "third-party-two/submodules/*"
}

This feature would be useful for quickly hopping between projects without needing to open new VS Code windows or manually copy the settings from nested workspaces. When working out of one code base for a while, I'm happy using the single workspace to do debugging and unit testing. To debug two code bases together, I need to either launch two VS Code windows for the respective workspaces, or I need to copy all the tasks and launches to a "root" workspace.

I find the latter option more convenient. I open a single VS Code at the root of all my repositories and manually copy in tasks and launches so that I can use the Debug tab to build, launch, and debug any subproject. But this leads to two problems; keeping the manual copy updated is hard, and updates to a build or task need to happen in the specific project's setting and then also in the root workspace settings.

[IllusionMH]

Looks like duplicate of #32693 or at least related

[hediet]

/duplicate #32693

[vscodenpa]

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!