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

Added the 404 component #305

Merged
merged 2 commits into from
Feb 18, 2020
Merged

Conversation

elit-altum
Copy link
Member

Created a newly designed 404 page for handling unspecified routes.
Fixes #275

File-animation-2

@netlify
Copy link

netlify bot commented Feb 12, 2020

Deploy preview for donut-frontend-r ready!

Built with commit 3c96599

https://deploy-preview-305--donut-frontend-r.netlify.com

@jaskiratsingh2000
Copy link
Member

@devesh-verma can you take a look once. Thanks

Copy link
Member

@devesh-verma devesh-verma left a comment

Choose a reason for hiding this comment

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

LGTM

@@ -15,6 +16,7 @@ const Router = () => (
<Route exact path="/pinned-posts" component={PinnedPosts} />
<Route exact path="/profile" component={Profile} />
<Route exact path="/organization" component={Organization} />
<Route component={NotFound} />
Copy link
Member

Choose a reason for hiding this comment

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

path is missing for not found route that is 404

Copy link
Member Author

Choose a reason for hiding this comment

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

Sir no specific path is required there. The component 'NotFound' will render at every path not already specified above it. Therefore showing a 404 error for every route which is not specified in the app, and the user tries to access it.

Copy link
Member

Choose a reason for hiding this comment

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

so usually, I have seen route as * for 404, please let me know if its not needed so that I can merge.

@devesh-verma
Copy link
Member

@elit-altum can please resolve the merge conflict and update the PR.

@elit-altum elit-altum force-pushed the 404-Component branch 2 times, most recently from 085d3ac to d331739 Compare February 18, 2020 15:32
@devesh-verma devesh-verma merged commit 242f312 into codeuino:development Feb 18, 2020
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.

3 participants