This event signals that some state in the debug adapter has changed and requires that the client needs to re-render the data snapshot previously requested.
Debug adapters do not have to emit this event for runtime changes like stopped or thread events because in that case the client refetches the new state anyway. But the event can be used for example to refresh the UI after rendering formatting has changed in the debug adapter.
This event should only be sent if the debug adapter has received a value true for the 'supportsInvalidatedEvent' capability of the 'initialize' request.
*/
exportinterfaceInvalidatedEventextendsEvent{
// event: 'invalidated';
body:{
/** Optional set of logical areas that got invalidated. If this property is missing or empty, a single value 'all' is assumed. */
areas?:InvalidatedAreas[];
/** If specified, the client only needs to refetch data related to this thread. */
threadId?:number;
/** If specified, the client only needs to refetch data related to this stack frame (and the 'threadId' is ignored). */
stackFrameId?:number;
};
}
/** RunInTerminal request; value of command field is 'runInTerminal'.
This optional request is sent from the debug adapter to the client to run a command in a terminal.
This is typically used to launch the debuggee in a terminal provided by the client.