-
Notifications
You must be signed in to change notification settings - Fork 173
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
chore: report error url on fetchUrlStream exception #261
Conversation
Hello, can you fix the conflict please? |
@aduh95 Updated. It seems the other place has been fixed by another PR. |
Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
I pushed a new commit to try fix typecheck. |
Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
if (!(statusCode >= 200 && statusCode < 300)) | ||
return reject(new Error(`Server answered with HTTP ${statusCode}`)); | ||
const statusCode = response.statusCode; | ||
if (statusCode != null && statusCode >= 200 && statusCode < 300) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aduh95 just curious why eqeq is allowed? usually js/ts projects force eqeqeq instead of eqeq to avoid implicit conversions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIRC it’s allowed only for null
, because it’s the only value for which it’s useful instead of being confusing.
FOR ISSUE LOCATING...