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
Start debugging a node application (for example our express sample) or some Chrome application (for example our Renderer by launching "Debug VSCode Main and Renderer" from vscode repo)
Verify when you add a breakpoint on a line that we:
render breakpoint candidate locations in gray
breakpoint candidate locations give nice visual feedback so user can easily figure out they are clickable
clicking on the candiadte location adds a breakpoin, or if the breakpoint is already there it removes it
you can right click on the inline breakpoint and all the actions in the context menu make sense and work as expected
making changes to the editor content all the inline breakpoint decoration are nicely moved
making any changes to the breakpoints in the BREAKPOINT view nicely updates all the inline breakpoint decorations
when you stop debugging, or when you remove breakpoints from a line all the candidate decorations get removed
try to be creative and break the decoration UI. Also we were inspired by how Chrome is doing this, so you can always double check how chrome is behaving if you think we are inferior in some cases.
The text was updated successfully, but these errors were encountered:
Refs: #31612
Complexity: 4
Start debugging a node application (for example our express sample) or some Chrome application (for example our Renderer by launching "Debug VSCode Main and Renderer" from vscode repo)
Verify when you add a breakpoint on a line that we:
The text was updated successfully, but these errors were encountered: