Clear and concise description of the problem
As a developer using MF and react-bridge, I want to be able to externally manage the loading and fallback states, so that I could use the same loading or fallback state until the remote component internals have finished loading.
We have a case, where we have to show a loading state inside the host, because the remote is still loading (shadow dom) styles. We could disable the react-bridge loading state and use our own, but this results in an issue, where if the remote fails to load and the fallback triggers, the loading state is still true, so both the fallback and loading state are rendered.
Suggested solution
Make the boundary and fallback on react bridge optional, so the host can handle the boundary itself.
Alternative
Somehow notify the host, that the error boundary triggered while also showing the defined fallback.
Additional context
No response
Validations
Clear and concise description of the problem
As a developer using MF and react-bridge, I want to be able to externally manage the loading and fallback states, so that I could use the same loading or fallback state until the remote component internals have finished loading.
We have a case, where we have to show a loading state inside the host, because the remote is still loading (shadow dom) styles. We could disable the react-bridge loading state and use our own, but this results in an issue, where if the remote fails to load and the fallback triggers, the loading state is still true, so both the fallback and loading state are rendered.
Suggested solution
Make the boundary and fallback on react bridge optional, so the host can handle the boundary itself.
Alternative
Somehow notify the host, that the error boundary triggered while also showing the defined fallback.
Additional context
No response
Validations