-
Notifications
You must be signed in to change notification settings - Fork 92
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: error page #301
feat: error page #301
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.
Great Work, I have a comment.
@@ -96,6 +97,7 @@ const getRoutesList = () => { | |||
path="/profile/:gtfsRideGtfsRouteId" | |||
key={'/profile/:gtfsRideGtfsRouteId'} | |||
element={<Profile />} | |||
ErrorBoundary={ErrorPage} |
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.
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 meant even when the backend is off , this error page is not displayed. From first look of it, we don't catch errors from axios requests. Up to you, if you would like to do it as part of this pr or we can clarify it in the issue that this is left to do.
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.
That's a great idea actually.
This error boundary build for handling js exceptions rather than network errors, but it's definitely something we should consider
Description
#273
screenshots