We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
sendWithUs.send
5.1.0
The callback passed to sendWithUs.send(data, callback) should always be called
sendWithUs.send(data, callback)
The callback is not called when there is an error that prevents any response from the server (such as ETIMEDOUT)
ETIMEDOUT
Induce a network error in the request flow.
A .catch(err => callback(err) or similar should be added to:
.catch(err => callback(err)
https://github.com/sendwithus/sendwithus_nodejs/blob/master/lib/sendwithus.js#L150-L154
The text was updated successfully, but these errors were encountered:
Thanks for bringing this to our attention. We will add this within the next two weeks, I'll link back to the issue with the PR when it's available
Sorry, something went wrong.
this has been covered in the 6.0.0 release done in PR #61
No branches or pull requests
Client version
5.1.0
Expected behaviour
The callback passed to
sendWithUs.send(data, callback)
should always be calledActual behaviour
The callback is not called when there is an error that prevents any response from the server (such as
ETIMEDOUT
)Steps to reproduce
Induce a network error in the request flow.
Recommendation
A
.catch(err => callback(err)
or similar should be added to:https://github.com/sendwithus/sendwithus_nodejs/blob/master/lib/sendwithus.js#L150-L154
The text was updated successfully, but these errors were encountered: