-
Notifications
You must be signed in to change notification settings - Fork 142
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
Add fallback components to selected part of the UI #1247
Labels
Comments
sarathms
added
discuss
invites discussion from contributors
effort/L
ooni/probe-desktop
priority/low
ux
labels
Sep 8, 2020
This may also be relevant to Explorer |
Related issue for explorer: ooni/explorer#516 |
hellais
modified the milestones:
Sprint 26 - Neerali,
Sprint 27 - Hexacorallia,
Sprint 28 - Corallimorpharia
Nov 23, 2020
sarathms
modified the milestones:
Sprint 37 - Vampire squid,
Sprint 38 - Umbrella octopus
Apr 26, 2021
sarathms
modified the milestones:
Sprint 46 - Happy Oyster,
Sprint 47 - Caribbean Reef Octopus
Aug 30, 2021
sarathms
modified the milestones:
Sprint 47 - Caribbean Reef Octopus,
Sprint 48 - Amazon river dolphin
Sep 13, 2021
sarathms
modified the milestones:
Sprint 48 - Amazon river dolphin,
Sprint 49 - Humpback whale
Sep 27, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
While researching solutions for #1245, I came across
react-error-boundary
which provides an API to setup fallback UI to mount when the app encounters runtime errors in renders. It doesn't make sense to use it at very granular level like in the below example, but it might be useful to implement at a higher level and provide a graceful way to recover when test results contain unexpected values or expected values are absent. Of course, some UX brainstorming is needed to identify which parts of UI warrant a fallback version.Stable UI
Fallback component (only contains a simple string here) when any of the 4 values in the columns throw unhandled exceptions.
The text was updated successfully, but these errors were encountered: