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

fix: introduce proper error boundary #2582

Merged
merged 1 commit into from
Mar 6, 2024
Merged

Conversation

mstykow
Copy link
Member

@mstykow mstykow commented Feb 23, 2024

Summary of changes

  • add methods to quit or relaunch the app
  • create error boundary that displays error and offers options to relaunch or quit

image

Context and reason for change

closes #2564

How can the changes be tested

You must produce an unexpected error. For example, you could start the app locally and change the code somewhere to break it, e.g., put this into ReportView to trigger an unexpected error when the user switches to report view: console.log(null.map())

@mstykow mstykow linked an issue Feb 23, 2024 that may be closed by this pull request
@alexzurbonsen
Copy link
Contributor

Nice. Lgtm (Before the most recent rebase at least...)

@mstykow mstykow force-pushed the feat-opossumui-2.0 branch 14 times, most recently from e49bc07 to 2ec903d Compare March 4, 2024 10:33
@mstykow mstykow force-pushed the fix-error-boundary branch from 5981eaf to 650f332 Compare March 4, 2024 11:05
@mstykow mstykow force-pushed the feat-opossumui-2.0 branch 2 times, most recently from c9b54aa to a0de24d Compare March 4, 2024 18:56
@mstykow mstykow force-pushed the fix-error-boundary branch from 650f332 to c63f6f3 Compare March 4, 2024 18:59
@mstykow mstykow force-pushed the feat-opossumui-2.0 branch 3 times, most recently from 72eb751 to 7c556e9 Compare March 5, 2024 13:38
@mstykow mstykow force-pushed the fix-error-boundary branch from c63f6f3 to eab880b Compare March 5, 2024 13:40
@mstykow mstykow force-pushed the feat-opossumui-2.0 branch 4 times, most recently from 99140be to f2c7fc3 Compare March 5, 2024 19:33
@mstykow mstykow force-pushed the fix-error-boundary branch from eab880b to 397ecff Compare March 5, 2024 19:34
@mstykow mstykow force-pushed the feat-opossumui-2.0 branch from f2c7fc3 to 0c6d8c5 Compare March 6, 2024 10:01
@mstykow mstykow force-pushed the fix-error-boundary branch from 397ecff to 18abc69 Compare March 6, 2024 10:09
@mstykow mstykow force-pushed the feat-opossumui-2.0 branch 2 times, most recently from 3c02b80 to d26f86d Compare March 6, 2024 16:42
@mstykow mstykow force-pushed the fix-error-boundary branch from 18abc69 to 7b7605b Compare March 6, 2024 16:43
@mstykow mstykow force-pushed the feat-opossumui-2.0 branch from d26f86d to d0c56c4 Compare March 6, 2024 17:04
@mstykow mstykow force-pushed the fix-error-boundary branch from 7b7605b to 742d223 Compare March 6, 2024 17:05
- add methods to quit or relaunch the app
- create error boundary that displays error and offers options to relaunch or quit

closes #2564

Signed-off-by: Maxim Stykow <maxim.stykow@tngtech.com>
@mstykow mstykow force-pushed the fix-error-boundary branch from 742d223 to 873d5cf Compare March 6, 2024 17:16
@mstykow mstykow merged commit a9de25d into feat-opossumui-2.0 Mar 6, 2024
5 checks passed
@mstykow mstykow deleted the fix-error-boundary branch March 6, 2024 17:16
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.

Create a proper error boundary
2 participants