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
weinand opened this issue
Jan 26, 2018
· 1 comment
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebtCode quality issuesdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
Editing the "condition" or "hitCondition" on a breakpoint does not preserve the identity of a breakpoint (aka uuid) but results in a remove and then an add event. I would expect to receive a changed event instead (as I do when the enable state changes).
This behaviour is undesirable and surfaces now in the extension API for breakpoints.
The text was updated successfully, but these errors were encountered:
weinand
added
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
labels
Jan 26, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugdebtCode quality issuesdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
Editing the "condition" or "hitCondition" on a breakpoint does not preserve the identity of a breakpoint (aka uuid) but results in a remove and then an add event. I would expect to receive a changed event instead (as I do when the enable state changes).
This behaviour is undesirable and surfaces now in the extension API for breakpoints.
The text was updated successfully, but these errors were encountered: