-
Notifications
You must be signed in to change notification settings - Fork 296
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
Conversation
@microsoft-github-policy-service agree |
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.
Thanks for the PR! Some comments 🙂
src/ui/customBreakpointsUI.ts
Outdated
}), | ||
); | ||
|
||
context.subscriptions.push( | ||
vscode.commands.registerCommand(Commands.RemoveAllCustomBreakpoints, () => { | ||
provider.removeBreakpoints(provider.breakpoints.filter(b => b.enabled).map(b => b.id)); | ||
provider.removeBreakpoints( | ||
provider.breakpointCategories |
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.
Wouldn't this only remove categories that have all of their children checked, and not individual children?
Can we put XHR breakpoints into a separate PR to keep this one focused on the existing changes? |
|
"Browser Breakpoints", renamed to "Event Listener Breakpoints", are now organized in a tree-view structure, utilizing the new Treeview-Checkbox API
