-
Notifications
You must be signed in to change notification settings - Fork 207
Open
Description
Describe the bug
The ErrorBoundary of the library is not letting my error propagate up to the global ErrorBoundary.
This is resulting in customers seeing this plain "Error Rendering Component" screen.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
- Have a global error boundary on your app
- Have a feature using the FlexLayout library
- Force a crash in the feature
- Notice that the FlexLayout ErrorBoundary catches the error, not the global ErrorBoundary.
Ex:
if (shouldCrash) {
throw new Error('Test error for error boundary testing');
}
Expected behavior
As a user, FlexLayout cannot be catching my error boundaries for unrelated issues. This is causing us to show that Error Rendering Component screen to users.
Operating System
macOS
Browser Type?
Google Chrome
Browser Version
138.0.7204.101
Screenshots or Videos
Additional context
No response
Metadata
Metadata
Assignees
Labels
No labels