-
Notifications
You must be signed in to change notification settings - Fork 300
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
Question about exception handling #503
Labels
Comments
Never mind, I found that there is BindTry. I initially did not find it, because it's not in the docs. But I did find it in the source code. Perhaps it should be mentioned in the docs. |
Yeah, the docs are lacking, that's true. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I had a call to
Map
in my chain, but the callback was throwing an exception. I was expecting for the exception to be caught internally and for the result to be errored out to the exception message, but that didn't happen and it just threw the exception into my code. That's understandable, but my question is what is the recommended way to handle exceptions inside callbacks/lambdas so that the error gets set properly into the result?The text was updated successfully, but these errors were encountered: