-
-
Notifications
You must be signed in to change notification settings - Fork 935
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 have undefined body when using streams #1138
Comments
This has been also fixed in #1051 |
You need to access the response via |
Is this going to be consistent in future versions? Or is it going to change in #1051 ? |
I don't know exactly what do you mean, but this issue is fixed in #1051. |
I meant currently I am asking because if it's going to change, we will also need to change code. |
|
Cool. I will disregard the docs then. I am doing coding as per |
Btw, I found another bug. Even if |
yes, it'd be best to include some reproducible code (but I think I can sketch something on my own so that's not necessary, but it will be welcome) |
Opened #1142 |
Describe the bug
Actual behavior
When
isStream: true
is set and request results in HTTPError, the stream emitserror
event. The emit handler is only called witherror
argument andbody
andresponse
arguments areundefined
....
Expected behavior
As per the docs, the
body
andresponse
arguments should be set witherror
event....
Code to reproduce
Checklist
The text was updated successfully, but these errors were encountered: