-
Notifications
You must be signed in to change notification settings - Fork 78
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.
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
Proposed protocol addition "set-next-statement" #28 #45
Conversation
LGTM |
/** A GotoTarget describes a code location that can be used as a target in the 'goto' request. | ||
The possible goto targets can be determined via the 'gotoTargets' request. | ||
*/ | ||
export interface GotoTarget { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We also need a 'label' string to provide a disambiguation dialog if there is more than one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gregg-miskelly yes, makes sense and brings it closer to the similar StepInTarget
.
IMHO, I think it would be better to adopt the VS model here. Essentially, you'd just need a GotoRequest that takes the file path and line number and can handle errors. |
@jacdavis that wouldn't work very well with trying to build a debug engine that exposes out the debug protocol - AD7 has a bunch of different SetNextStatement related methods (EnumCodeContexts, CanSetNextStament, IDebugCodeContex2.Compare, SetNextStatement) with a disambiguation dialog in between some of them. I think we can safely combine EnumCodeContexts+CanSetNextStatement in the enumeration API. But I think if we try and combine them all together will not be able to create a debug engine that can support this. |
That’s right, I forgot about EnumCodeContexts. I guess we already have the scalability issue even in vs. From: Gregg Miskelly [mailto:notifications@github.com] @jacdavishttps://github.com/jacdavis that wouldn't work very well with trying to build a debug engine that exposes out the debug protocol - AD7 has a bunch of different SetNextStatement related methods (EnumCodeContexts, CanSetNextStament, IDebugCodeContex2.Compare, SetNextStatement) with a disambiguation dialog in between some of them. I think we can safely combine EnumCodeContexts+CanSetNextStatement in the enumeration API. But I think if we try and combine them all together will not be able to create a debug engine that can support this. — |
I've merged the PR and added a |
Protocol addition "set-next-statement" (#28) contains:
supportsGotoTargetsRequest
capabilityGotoTarget
gotoTargetsRequest
requestGotoRequest
request