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: Tidying Up of Instrumentation Breakpoints #1853

Merged
merged 13 commits into from
Oct 23, 2023

Conversation

OnesAndZer0s
Copy link
Contributor

@OnesAndZer0s OnesAndZer0s commented Oct 17, 2023

"Browser Breakpoints", renamed to "Event Listener Breakpoints", are now organized in a tree-view structure, utilizing the new Treeview-Checkbox API
image

@OnesAndZer0s
Copy link
Contributor Author

@microsoft-github-policy-service agree

Copy link
Member

@connor4312 connor4312 left a comment

Choose a reason for hiding this comment

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

Thanks for the PR! Some comments 🙂

}),
);

context.subscriptions.push(
vscode.commands.registerCommand(Commands.RemoveAllCustomBreakpoints, () => {
provider.removeBreakpoints(provider.breakpoints.filter(b => b.enabled).map(b => b.id));
provider.removeBreakpoints(
provider.breakpointCategories
Copy link
Member

Choose a reason for hiding this comment

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

Wouldn't this only remove categories that have all of their children checked, and not individual children?

@OnesAndZer0s OnesAndZer0s changed the title Tidying Up of Instrumentation Breakpoints feat: Tidying Up of Instrumentation Breakpoints & XHR/fetch breakpoints Oct 19, 2023
@connor4312
Copy link
Member

Can we put XHR breakpoints into a separate PR to keep this one focused on the existing changes?

@OnesAndZer0s OnesAndZer0s changed the title feat: Tidying Up of Instrumentation Breakpoints & XHR/fetch breakpoints feat: Tidying Up of Instrumentation Breakpoints Oct 19, 2023
@OnesAndZer0s
Copy link
Contributor Author

Can we put XHR breakpoints into a separate PR to keep this one focused on the existing changes?

#1856

@connor4312 connor4312 enabled auto-merge October 23, 2023 17:00
@connor4312 connor4312 added this to the October 2023 milestone Oct 23, 2023
@connor4312 connor4312 merged commit aa1cd44 into microsoft:main Oct 23, 2023
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.

3 participants