- Notifications
You must be signed in to change notification settings - Fork928
chore: ui error handling should be specific to general#14346
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Specific errors should be checked before defaulting to a generalerror handling
alwaysmeticulousbot commentedAug 19, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
✅ Meticulous spotted zero visual differences across 1477 screens tested:view results. Meticulous tested100% of the executable lines edited in this PR. Expected differences?Click here. Last updated for commit1b39235. This comment will update as new commits are pushed. |
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.
Do you think you could add a test for this?
Uh oh!
There was an error while loading.Please reload this page.
Added a story book 👍 |
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.
thanks for the test!
755afa3
intomainUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Specific errors should be checked before defaulting to a general error handling.
I noticed the error details were not being shown in my manual testing. We should check for axios error before defaulting to a general string.