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
feat: http error handling without retries #226
Conversation
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.
LGTM
actions/AuthAction.js
Outdated
}) | ||
.get() | ||
.json(); | ||
const { valid } = response; |
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.
return response.valid
?
actions/Network.js
Outdated
.resolve((_) => _.setTimeout(REQUEST_TIMEOUT)) | ||
.resolve((_) => { | ||
return _.fetchError((error) => { |
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.
Generally, _ is used as a placeholder for unused parameter. However, using _ in this way creates confusion as to why a method is called on it. I would have preferred a parameter name such as request
.
web-src/src/helpers/NetworkHelper.js
Outdated
.resolve((_) => { | ||
return _ |
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.
I would have preferred a parameter name such as request
.
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.
Left some minor comments.
Description
What's inside:
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: