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 changed the debug protocol and VS Code debug UI to allow debug adapters to return a "lazy" variable, which will not have its real value retrieved until the user clicks a button. No "real" debug adapters have implemented this feature yet, so you can test it with the vscode-mock-debug.
In the variables view, the variable should not have its real value, but a (...) button. When you click it, the real value should appear
Test this variable in all places in the debug UI where a variable appears:
Watch, Debug Console, hover: you should see the real value immediately with no button
Inline debug values (debug.inlineValues): you should see a placeholder value returned by the DA, in mock-debug's case, "lazy var". When expanding the value in the variables view, the inline value should change
When stepping, an expanded lazy var in the variables view should go back to its unexpanded state with the button
The text was updated successfully, but these errors were encountered:
Refs: #134450
Complexity: 3
Create Issue
We have changed the debug protocol and VS Code debug UI to allow debug adapters to return a "lazy" variable, which will not have its real value retrieved until the user clicks a button. No "real" debug adapters have implemented this feature yet, so you can test it with the vscode-mock-debug.
(...)
button. When you click it, the real value should appeardebug.inlineValues
): you should see a placeholder value returned by the DA, in mock-debug's case, "lazy var". When expanding the value in the variables view, the inline value should changeThe text was updated successfully, but these errors were encountered: