-
Notifications
You must be signed in to change notification settings - Fork 331
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
Errors not captured in methods? #809
Comments
It’s intended - Bacon has never caught exceptions. The thinking is that exceptions are treated as programming errors and should fail fast. Which is ofc opinionated. |
Thanks for the insight, seems reasonable |
@jaidetree Otherwise you can use
|
That's perfect thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given code like the following:
I expect the error in the map operator to make its way through the promise, then the catch handler can test the error and log my expected message.
Instead, the stream exits immediately and it seems like an error is thrown outside of the stream.
Is the idea that I should be wrapping my logic in a try...catch clause or is this an unexpected bug?
The text was updated successfully, but these errors were encountered: