You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Child MFE is no different than any other MFE except that it can define a component that can then be pass into the Host MFE
298
+
The Child MFE is no different than any other MFE except that it can define a `Plugin` component that can then be pass into the Host MFE
299
299
as an iFrame-based plugin via a route.
300
300
This component communicates (via ``postMessage``) with the Host MFE and resizes its content to match the dimensions
301
301
available in the Host's plugin slot.
302
302
303
+
Fallback Behavior
304
+
-----------------
305
+
306
+
Setting a Fallback component
307
+
''''''''''''''''''''''''''''
308
+
The two main places to configure a fallback component for a given implementation are in the PluginSlot props and in the JS configuration. The JS configuration fallback will be prioritized over the PluginSlot props fallback.
309
+
310
+
PluginSlot props
311
+
````````````````
312
+
This is ideally used when the same fallback should be applied to all of the plugins in the `PluginSlot`. To configure, set the `slotErrorFallbackComponent` prop in the `PluginSlot` to a React component. This will replace the default `<ErrorPage />` component from frontend-platform.
Can be used when setting a fallback for a specific plugin within a slot. Set the `errorFallbackComponent` field for the specific plugin to the custom fallback component in the JS configuration. This will be prioritized over any other fallback components.
0 commit comments