-
Notifications
You must be signed in to change notification settings - Fork 6
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
fix: Redirect to 404 Page When Note is Not Found #277
base: main
Are you sure you want to change the base?
Conversation
Tushar504
commented
Nov 16, 2024
- This PR adds try catch block to redirect user to 404 not found error page as described in Issue Closes Redirect to 404 Page When Note is Not Found #276
- updates the useNote service load method.
src/application/services/useNote.ts
Outdated
noteTools.value = response.tools; | ||
parentNote.value = response.parentNote; | ||
} catch (error) { | ||
void router.push('/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.
I'd suggest to separate 4xx errors and other errors. If 4xx error happen, show 404 error page. In case of other errors, show 500 "Unexpected error" page
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.
request you to review new changes
src/application/router/routes.ts
Outdated
path: '/error', | ||
component: ErrorPage, | ||
meta: { | ||
layout: 'fullpage', | ||
pageTitleI18n: 'pages.notFound', | ||
pageTitleI18n: 'pages.error', | ||
discardTabOnLeave: true, | ||
}, | ||
props: { | ||
code: 404, | ||
}, | ||
props: route => ({ | ||
code: route.query.code, | ||
customMessage: route.query.message, | ||
}), |
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.
404 page was actually needed (this was a syntax for each unexpected url, that would show 404 page not found
)
we need to create separate /error page, that should have statusCode
property and show different info by different status code
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.
also better to use route.params for code
prop
/** | ||
* Domain error thrown when unknown error occurs | ||
*/ | ||
export default class ApiError extends DomainError { | ||
/** |
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 think, that DomainError
actually extends ApiError
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.
Actually, currently it is not needed, I had created the ApiError to consider it as default error, to check api error response is instance of ApiError or not,
parentNote.value = response.parentNote; | ||
} catch (error) { | ||
if (error instanceof NotFoundError) { | ||
void router.push(`/error/404?message=${error.message}`); |
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.
It's better to specify error message directly, instead of using error.message
. And use i18n for that.
Other code looks good for me