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.

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

feat: implement step in targets #1307

Merged
merged 3 commits into from
Jun 24, 2022
Merged

feat: implement step in targets #1307

merged 3 commits into from
Jun 24, 2022

Conversation

connor4312
Copy link
Member

For microsoft/vscode#123879

It uses possible breakpoint locations to extra and display possible step ranges. It tries to parse the source line to get the appropriate label and range to return to VS Code, which works pretty well in my testing.

image

Step into works similarly to what core does in "run to line" -- it sets a breakpoint on the desired location, resumes the debugger (skipping all pauses until the breakpoint is hit), then removes the breakpoint and steps in.

@connor4312 connor4312 self-assigned this Jun 14, 2022
/**
* Gets a "step into" target at the given offset in the line of code.
*/
export function getStepTargetInfo(line: string, offset: number) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this still going to return breakpoint locations that are not step into targets? I'm not sure

@connor4312 connor4312 merged commit 0d3d73c into main Jun 24, 2022
@connor4312 connor4312 deleted the feat/step-in-targets branch June 24, 2022 22:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants