The currently active debug console.
The currently active debug session or undefined. The active debug session is the one
represented by the debug action floating window or the one currently shown in the drop down menu of the debug action floating window.
If no debug session is active, the value is undefined.
List of breakpoints.
Add breakpoints.
The breakpoints to add.
An event which fires when the active debug session
has changed. Note that the event also fires when the active debug session changes
to undefined.
An event that is emitted when the set of breakpoints is added, removed, or changed.
An event which fires when a custom DAP event is received from the debug session.
An event which fires when a new debug session has been started.
An event which fires when a debug session has terminated.
Register a debug adapter descriptor factory for a specific debug type. An extension is only allowed to register a DebugAdapterDescriptorFactory for the debug type(s) defined by the extension. Otherwise an error is thrown. Registering more than one DebugAdapterDescriptorFactory for a debug type results in an error.
The debug type for which the factory is registered.
The debug adapter descriptor factory to register.
A disposable that unregisters this factory when being disposed.
Register a debug adapter tracker factory for the given debug type.
The debug type for which the factory is registered or '*' for matching all debug types.
The debug adapter tracker factory to register.
A disposable that unregisters this factory when being disposed.
Register a debug configuration provider for a specific debug type.
The optional triggerKind can be used to specify when the provideDebugConfigurations method of the provider is triggered.
Currently there are two situations:
(1) providing debug configurations to populate a newly created launch.json
(2) providing dynamically generated configurations when the user asks for them through the UI (e.g. via the "Select and Start Debugging" command).
Please note that the triggerKind argument only applies to the provideDebugConfigurations method, the resolveDebugConfiguration methods are not affected at all.
Registering a single provider with resolve methods for different trigger kinds results in the same resolve methods being called multiple times.
More than one provider can be registered for the same type.
The debug type for which the provider is registered.
The debug configuration provider to register.
The {@link DebugConfigurationProviderTrigger trigger} for which the 'provideDebugConfiguration' method of the provider is registered. If triggerKind is missing, the value DebugConfigurationProviderTriggerKind.Initial is assumed.
A Disposable that unregisters this provider when being disposed.
Remove breakpoints.
The breakpoints to remove.
Start debugging by using either a named launch or named compound configuration, or by directly passing a DebugConfiguration. The named configurations are looked up in '.vscode/launch.json' found in the given folder. Before debugging starts, all unsaved files are saved and the launch configurations are brought up-to-date. Folder specific variables used in the configuration (e.g. '${workspaceFolder}') are resolved against the given folder.
The workspace folder for looking up named configurations and resolving variables or undefined for a non-folder setup.
Either the name of a debug or compound configuration or a DebugConfiguration object.
A thenable that resolves when debugging could be successfully started.
Namespace for debug functionality.