"Breakpoints view" is not accessible unless setting at least one, thus restricting to access to "Exceptions"

[nicolasmol]

Not sure it was always like this before, but look at this.
Unless I set at least one breakpoint, it's not possible to show the "Breakpoints view" in the panel.
Then its the only solution to toggle (All/Uncaught Exceptions).
Was not possible to show this view without any user predefined breakpoints ?

Flutter 3.3.7 • channel stable • https://github.com/flutter/flutter.git
Framework • revision e99c9c7cd9 (il y a 3 semaines) • 2022-11-01 16:59:00 -0700
Engine • revision 857bd6b74c
Tools • Dart 2.18.4 • DevTools 2.15.0
Vscode: 1.73.1
OS: Linux Mint 20.3 x86_64 Kenel 5.15.0-53-generic

[roblourens]

Not sure about this- did you move the breakpoints view into the test view? Does it work in the debug viewlet?

[nicolasmol]

Not sure what you mean. Maybe larger screens captures will help.
Do you see the "debug viewlet <= if it's so called" is not accessible in the menu when no breakpoint is defined

But when is set one breakpoint, it appears in the menu & the viewlet also

But this means that if you want to switch theses checkboxes :

...you must need to define at least a breakpoint !!

Is this not 2 extras click ?

1. turn on a dummy a breakpoint <===== ???
2. switch the desired type of exception
3. turn off the dummy breakpoint <===== ???

[nicolasmol]

Side note...
It appears that the problem was in my current Flutter project but not now ...opening another one.

I briefly checked if its a matter of path/symlink...this doesn't seem to be.

Would it be because of one dependency ?

[nicolasmol]

How strange is this...I show you side by side
On the left : freshly made project "test" => Debug viewlet not accessible in the right-click menu
path is : /home/nicolasm/Dev/Flutter Courses/Dbestech/test
On the right: an old project : => Debug viewlet is accessible in the right-click menu
path is: /home/nicolasm/Dev/Flutter Courses/Dbestech/Quiz app wih firebase

[roblourens]

I see, this happens when you don't have a launch.json in your project. Since it's possible to debug without defining a launch.json, we should show this view when you have started the debugger once previously.

[roblourens]

If anyone wants to work on this, we should add a new context key that is set to true when a debug session starts, and when that context key is true, the breakpoints view should be visible:

vscode/src/vs/workbench/contrib/debug/browser/debug.contribution.ts

Line 412 in ffff626

viewsRegistry.registerViews([{ id: BREAKPOINTS_VIEW_ID, name: nls.localize('breakpoints', "Breakpoints"), containerIcon: icons.breakpointsViewIcon, ctorDescriptor: new SyncDescriptor(BreakpointsView), order: 40, weight: 20, canToggleVisibility: true, canMoveView: true, focusCommand: { id: 'workbench.debug.action.focusBreakpointsView' }, when: ContextKeyExpr.or(CONTEXT_BREAKPOINTS_EXIST, CONTEXT_DEBUG_UX.isEqualTo('default')) }], viewContainer);

[MonadChains]

@roblourens I've submit a patch with a possible fix, let me know if it works.