Skip to content

Need to be able to disable the ErrorBoundary #501

@JoeVanGundy

Description

@JoeVanGundy

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.

Image

Your Example Website or App

No response

Steps to Reproduce the Bug or Issue

  1. Have a global error boundary on your app
  2. Have a feature using the FlexLayout library
  3. Force a crash in the feature
  4. 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

Image

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions