-
Notifications
You must be signed in to change notification settings - Fork 3
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
Refactor: improve no data response #838
Conversation
a942a2e
to
8451117
Compare
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.
Since you are changing some responses, I would add the changes of some messages to be clearer. Saying for example "Builds not found" for the builds of an issue makes it seem like an issue is supposed to have builds but they weren't found, which is not true. Saying "No builds found for this issue" doesn't imply anything, it just says that no builds were found.
8451117
to
413ae17
Compare
- create type to response with error prop - create function to throw a error message Part of #784
413ae17
to
8a8849d
Compare
8a8849d
to
2bd510f
Compare
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.
Nice changes. I just noticed that because of the thrown error there is a retry even if the status is 200, but this is the same as the current behavior so I'll approve
Create a issue for that #841 |
- change the status code from 404 to 200 (OK) - use makeRequest function to treat error from endpoint in the frontend - show error message in SectionError component Part of #784
2bd510f
to
6bbc998
Compare
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.
Worked well on my tests
Improve the response for not found data
Close #784