Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

support conditional breakpoints #6

Closed
weinand opened this issue Dec 27, 2015 · 5 comments
Closed

support conditional breakpoints #6

weinand opened this issue Dec 27, 2015 · 5 comments
Assignees
@weinand
Labels
feature-request Request for new features or functionality
Milestone
Jan 2016

Comments

@weinand
Copy link
Contributor

weinand commented Dec 27, 2015

extend the debug protocol to support conditional breakpoints (and other additional breakpoint attributes).
@weinand weinand added the feature-request Request for new features or functionality label Dec 27, 2015
@weinand weinand self-assigned this Dec 27, 2015
@weinand weinand added this to the Jan 2016 milestone Dec 27, 2015
@weinand
Copy link
Contributor Author

weinand commented Dec 27, 2015

fyi @isidorn

weinand added a commit to microsoft/vscode that referenced this issue Dec 27, 2015
@weinand
add support for conditiona breakpoints (see microsoft/vscode-debugada…
a85882a 
…pter-node#6)
@weinand weinand mentioned this issue Dec 27, 2015
Closed
@weinand weinand closed this as completed Dec 27, 2015
weinand added a commit to microsoft/vscode-node-debug that referenced this issue Dec 27, 2015
@weinand
add support for conditional breakpoints (microsoft/vscode-debugadapte…
c8d7980 
…r-node#6)
@daviwil daviwil mentioned this issue Dec 28, 2015
Closed
weinand added a commit that referenced this issue Dec 28, 2015
@weinand
add structured SourceBreakpoints (see #6)
71fb195
@isidorn
Copy link

isidorn commented Dec 28, 2015

@weinand looks good but why call it expression and not condition

@weinand
Copy link
Contributor Author

weinand commented Dec 28, 2015

@isidorn good question. Probably because the corresponding argument to the "evaluate" request is called "expression" too. But you are right, we should change this to condition.

@weinand
Copy link
Contributor Author

weinand commented Dec 28, 2015

@isidorn I've pushed the name change

@isidorn
Copy link

isidorn commented Dec 28, 2015

Thanks will adopt it right now

@egamma egamma mentioned this issue Jan 6, 2016
Closed
59 tasks
@egamma egamma mentioned this issue Feb 1, 2016
Closed
97 tasks
keradoracomb pushed a commit to keradoracomb/datasheet that referenced this issue Sep 19, 2023
add support for conditiona breakpoints (see microsoft/vscode-debugada…
0af29a4 
…pter-node#6)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@weinand weinand

Labels
feature-request Request for new features or functionality
Projects
None yet
Milestone
Jan 2016
Development

No branches or pull requests
2 participants
@weinand @isidorn