`debugger_compounds` purpose

[yaroslavyaroslav]

Hi, folks, thanks for great package port, I'm still trying to dig deep enough in it and can't find enough elaboration of debugger_compounds purpose in specific and debugger_configurations, debugger_tasks and debugger_compounds hierarchy in general?

As I can see in sublime-settings it's a composition of some strings, the one that reflects either tasks or configurations as I'm guessing. But the latter don't make sense to me, while the former seems as not the case, because of the single debugger_compounds property name.

Could you please elaborate it a bit?

[daveleroy]

It should be added to the readme.

A compound appear in the ui like any configuration and let you start multiple configurations at once.

{
   "name": "...", // Name of compound which appears in the launch configuration drop down menu.
   "configurations": [ "..."] // Names of configurations that compose this compound configuration
}

If you install LSP-json you should get auto complete for these

[yaroslavyaroslav]

Ok, that's make sense. So why would I need to start multiple configurations simultaneously? @daveleroy

[daveleroy]

For most people its probably not needed but developing client + server applications where you want to run and debug both at once or something like Electron which has multiple processes you want to debug at the same time.

Of course you can also just manually start multiple configurations if you want without compounds it just requires a lot of extra clicks.