Summary
Let ErrorBoundary render ChildContent, even one or more exceptions have been thrown.
Motivation and goals
We need a global exception handling in blazor that does not basically crash the whole app. With ErrorBoundary this is partly solved, but it require us to render something else than the components that throws the exception. We need to be able to continue to render components, even exceptions was thrown. This is to
In scope
- If for example a "Click to save" throws an exception, we don't wan't to loose the whole component state
- If data can't be loaded for the component, we want to render the component as it is before data is loaded
Out of scope
Risks / unknowns
Examples
<ErrorBoundary RenderOnException="true">...</ErrorBoundary>
Summary
Let ErrorBoundary render ChildContent, even one or more exceptions have been thrown.
Motivation and goals
We need a global exception handling in blazor that does not basically crash the whole app. With ErrorBoundary this is partly solved, but it require us to render something else than the components that throws the exception. We need to be able to continue to render components, even exceptions was thrown. This is to
In scope
Out of scope
Risks / unknowns
Examples
<ErrorBoundary RenderOnException="true">...</ErrorBoundary>