-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Dev mode which doesn't catch exceptions #1241
Labels
Comments
@NaridaL I see why the idea is relevant :). With the limatations of exception handling in JS it is really hard to find a behavior that works optimal for all causes. Feel free to attempt a pr, for example by introducing |
NaridaL
added a commit
to NaridaL/mobx
that referenced
this issue
Dec 4, 2017
NaridaL
added a commit
to NaridaL/mobx
that referenced
this issue
Dec 4, 2017
5 tasks
NaridaL
added a commit
to NaridaL/mobx
that referenced
this issue
Dec 4, 2017
Will be implemented in Mobx4. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've read #731, but the resolution isn't very satisfying. The current behavior makes debugging unnecessarily difficult.
extras.onReactionError(e =>{ throw e; });
makes things slightly better but doesn't fix the main issue that the debugger will not stop at the location of the actual error, but rather on the rethrow, which makes it impossible the inspect the values of the problematic stack frames.Halting on every exception will have one stepping through a bunch of caught exceptions in other frameworks which isn't helpful either.
The text was updated successfully, but these errors were encountered: