You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 11, 2020. It is now read-only.
Originally reported and contributed by @moritzraho
The doc states that only one debugger can be started per vscode window, which is not true anymore.
In fact, vscode debug config has the concept of compounds which allows to aggregate multiple configurations.
This also enables debugging for sequences OOTB (i.e. by starting a wskdebug instance for all the actions of a sequence). Which makes wskdebug even more useful :)
Here is a launch.json example that exposes a config starting 2 wskdebug instances:
Originally reported and contributed by @moritzraho
The doc states that only one debugger can be started per vscode window, which is not true anymore.
In fact, vscode debug config has the concept of
compounds
which allows to aggregate multiple configurations.This also enables debugging for sequences OOTB (i.e. by starting a wskdebug instance for all the actions of a sequence). Which makes wskdebug even more useful :)
Here is a launch.json example that exposes a config starting 2 wskdebug instances:
The text was updated successfully, but these errors were encountered: