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
We have introduced a new noCompact flag to the debugSessionOptions API. So get a VS Code starter extension, call the startDebugging api and pass the DebugSessionOptions such that you can verify the noCompact flag works as expected. For that you would have to call the startDebugging API twice and the second time pass a parentSession that you originaly created to establish a child - parent session relationship.
Verify:
if noCompact is present and set to true, the session shuold never be compacted with it's parent session
if noCompact is set to false or not set at all the session should be compacted with it's parent session
When sessions are compacted they are displayed as one element in the CALL STACK view
Please note that there is an additional test item about the CALL STACK view and the compacted elements. This one should only focus on testing the API.
Note: a simple way to use the startDebugging api is to simply pass the workspace folder and the name of an already existing launch configuration in your launch.json.
The text was updated successfully, but these errors were encountered:
Refs: #100852
Complexity: 3
Create Issue
We have introduced a new
noCompact
flag to thedebugSessionOptions
API. So get a VS Code starter extension, call thestartDebugging
api and pass theDebugSessionOptions
such that you can verify thenoCompact
flag works as expected. For that you would have to call thestartDebugging
API twice and the second time pass a parentSession that you originaly created to establish a child - parent session relationship.Verify:
noCompact
is present and set totrue
, the session shuold never be compacted with it's parent sessionnoCompact
is set tofalse
or not set at all the session should be compacted with it's parent sessionPlease note that there is an additional test item about the CALL STACK view and the compacted elements. This one should only focus on testing the API.
Note: a simple way to use the
startDebugging
api is to simply pass the workspace folder and the name of an already existing launch configuration in yourlaunch.json
.The text was updated successfully, but these errors were encountered: