-
Notifications
You must be signed in to change notification settings - Fork 56
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
Don't Throw on 500 Errors #136
Comments
I'm dealing with a particularly annoying server right now (PHP serialized data, bla bla bla), so I'm looking for some flexibility in my engine :) |
Yeah, I agree here, it's an async thing so throwing has unintended side-effects |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently resource.js does this on line 139:
We shouldn't throw in this case but let the engines handle it however they please.
The text was updated successfully, but these errors were encountered: