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

Improve Error and NotFound page - layout and informativeness #425

Open
ivan-aksamentov opened this issue Apr 6, 2020 · 1 comment
Open

Improve Error and NotFound page - layout and informativeness #425

ivan-aksamentov opened this issue Apr 6, 2020 · 1 comment

Comments

@ivan-aksamentov
Copy link
Member

@ivan-aksamentov ivan-aksamentov commented Apr 6, 2020

🙋 Feature Request

We need to imrove the usefullnes and user experience around Error and NotFound pages

🔦 Context

IMPORTANT: Before taking this issue, make sure you:

  • understand (or learn) how React error boundaries work
  • understand (or learn) how code splitting and lazy loading works
  • understand that the error and not found pages can be triggered in multiple ways
  • know how to run the app in production mode (see dev guide)
  • are able to test on desktop and mobile (at least in chrome dev tools)

😯 Describe the feature

  • in production, error page should contain basic information: what happened, how to report the bug and how to proceed
  • error page should contain a link or button-link to reload the main page
  • what are other error page best practices we can incorporate?
  • if you are knowledgeable in site monitoring and/or reliability, let us know what tools you would suggest to incorporate, so that we can set an account and/or infra (e.g. Sentry etc.)

💻 Examples

💁 Possible Solution

Related

@ivan-aksamentov ivan-aksamentov modified the milestones: 1.0, 1.1, 1.2 Apr 7, 2020
@ivan-aksamentov ivan-aksamentov modified the milestones: 1.1, 1.2 Apr 17, 2020
@ivan-aksamentov ivan-aksamentov mentioned this issue Apr 17, 2020
22 of 36 tasks complete
@ivan-aksamentov ivan-aksamentov removed this from the 1.2 milestone May 1, 2020
@Sa3ek8892
Copy link

@Sa3ek8892 Sa3ek8892 commented May 23, 2020

Ok

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.