If-Else in View？(If-Else in View?)

 https://code.visualstudio.com/docs/extensionAPI/api-debugging的以下部分解释了在遇到断点时会发生什么： 
 
 “每当程序停止时（在程序输入时，由于遇到断点，发生异常，或者用户请求执行暂停），调试适配器必须发送具有适当原因和线程ID的已停止事件。收到时VS代码将请求给定线程的堆栈跟踪（堆栈帧列表）。如果用户然后钻入堆栈帧，VS代码首先请求堆栈帧的范围，然后请求范围的变量。如果变量是VS Code本身是结构化的，它通过附加的变量请求来请求它的属性。这导致了以下层次结构：......“ 
 
 调试适配器测试在这里： https ： //github.com/Microsoft/vscode-node-debug/blob/master/src/tests/adapter.test.ts他们测试典型的VS代码方案。 您可能希望查看“应该在断点处停止”测试（第108行）。 
 
 为了节省空间，“停止原因”现在显示在CALL STACK视图的标题中： 
 
  

The following section from https://code.visualstudio.com/docs/extensionAPI/api-debugging explains what happens when a breakpoint is hit:
 
"Whenever the program stops (on program entry, because a breakpoint was hit, an exception occurred, or the user requested execution to be paused), the debug adapter has to send a stopped event with the appropriate reason and thread id. Upon receipt VS Code will request the stacktrace (a list of stack frames) for the given thread. If the user then drills into the stack frame, VS Code first requests the scopes for a stack frame, and then the variables for a scope. If a variable is itself structured, VS Code requests its properties through additional variables requests. This leads to the following hierarchy:..."
 
Debug adapter tests are here: https://github.com/Microsoft/vscode-node-debug/blob/master/src/tests/adapter.test.ts They test typical VS Code scenarios. You might want to look into the 'should stop on a breakpoint' test (line 108).
 
To save space the "stop reason" is now shown in the header of the CALL STACK viewlet: