-
Notifications
You must be signed in to change notification settings - Fork 0
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
Rework error handling #366
Labels
components
Regarding the components
Comments
Also, throwing an event would be useful so that the maintainer can catch and handle the error on a higher level if desired. |
fengelniederhammer
added a commit
that referenced
this issue
Aug 2, 2024
fengelniederhammer
added a commit
that referenced
this issue
Aug 2, 2024
fengelniederhammer
added a commit
that referenced
this issue
Aug 2, 2024
fengelniederhammer
added a commit
that referenced
this issue
Aug 20, 2024
fengelniederhammer
added a commit
that referenced
this issue
Aug 20, 2024
fengelniederhammer
added a commit
that referenced
this issue
Aug 20, 2024
fengelniederhammer
added a commit
that referenced
this issue
Aug 20, 2024
JonasKellerer
pushed a commit
that referenced
this issue
Aug 21, 2024
This was referenced Aug 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#143 added an error boundary to our components. Most of the errors will however just be displayed as "Whoops, something went wrong".
We should give the user more indication on what went wrong in the expected cases, i.e. throw more
UserFacingError
s.The text was updated successfully, but these errors were encountered: