Network errors not caught correctly #38
Comments
|
@adamdonahue the issues you were experiencing should be fixed in |
|
Fantastic. Thanks. You're quick; I was planning to take a look today
myself.
…On Thu, Nov 9, 2017 at 1:58 AM, Jayden Seric ***@***.***> wrote:
@adamdonahue <https://github.com/adamdonahue> the issues you were
experiencing should be fixed in ***@***.***
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#38 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACS4jkq7cv5BY5HBeIfpCh2Msc9VJe6iks5s0qKEgaJpZM4QXYfu>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See #35 (comment).
Apparently
.catch(observer.error)does not work the same as.catch(error => observer.error(error)).The text was updated successfully, but these errors were encountered: