Option to break on handled exceptions in Flutter framework

[mit-mit]

From @sethladd on January 29, 2016 18:29

From @sethladd on January 12, 2016 17:5

Was: dart-atom/dart#630

Flutter handles most (all?) exceptions thrown from user code. This is usually pretty great, except when I'm debugging. I want my app to stop at the point of the exception, so I can work on fixing it.

Normally, the editor can break on unhandled exceptions. But for handled exceptions, we might need to do something "Flutter aware".

Copied from original issue: dart-atom/atom-flutter#31

Copied from original issue: flutter/flutter#1476

[mit-mit]

From @Hixie on January 29, 2016 18:45

We could create a debugBreakOnException boolean in some low-level file and then have the various exception-catching methods call:

debugger(when: debugBreakOnExceptions);

[mit-mit]

From @Hixie on January 29, 2016 18:46

(and expose debugBreakOnExceptions as an extension that Atom can set)

[mit-mit]

From @eseidelGoogle on May 13, 2016 17:14

I'm not sure what this asking for. @devoncarew added the ability to have Atom break on all exceptions, did that solve this?

[alexander-doroshko]

VM Service protocol allows to choose how to stop on exceptions: All, Unhandled or None. Default in IntelliJ is Unhandled. I think an option in the IDE should be added to allow user to choose. Tracked as https://youtrack.jetbrains.com/issue/WEB-13268