Skip to content
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

Merged
merged 2 commits into from
Dec 16, 2023
Merged

feat: error page #301

merged 2 commits into from
Dec 16, 2023

Conversation

NoamGaash
Copy link
Member

Description

#273

screenshots

image

@NoamGaash NoamGaash requested a review from shootermv December 14, 2023 20:40
@NoamGaash NoamGaash linked an issue Dec 14, 2023 that may be closed by this pull request
Copy link
Collaborator

@ArkadiK94 ArkadiK94 left a 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}
Copy link
Collaborator

@ArkadiK94 ArkadiK94 Dec 16, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, is it the only route that we should add ErrorBoundary?
Not looks like it, I changed the VITE_BASE_PATH to be an uncorrect path and still I don't see any data and there is an error in the console...
image
image

Copy link
Collaborator

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.

Copy link
Member Author

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

@NoamGaash NoamGaash merged commit a2f93ea into main Dec 16, 2023
13 checks passed
@NoamGaash NoamGaash deleted the feat/error-page branch December 16, 2023 11:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add error boundary to display error message in case of server error
2 participants