Description
It seems that the main idea behind the generic ErrorPage component is to use it within MFEs as page content or as a section for displaying errors.
Currently, we can notice that many MFEs use their own custom-built components for error pages instead of the existing ErrorPage provided by frontend-platform. This may indicate several issues with the current component:
- insufficient flexibility;
- problems with visual presentation;
- error messages that are not clear enough.
It might be worth considering a rework of the ErrorPage component and adopting it as a single generic solution for displaying error pages (or sections) across all MFEs.
Some additional context
Description
It seems that the main idea behind the generic ErrorPage component is to use it within MFEs as page content or as a section for displaying errors.
Currently, we can notice that many MFEs use their own custom-built components for error pages instead of the existing ErrorPage provided by frontend-platform. This may indicate several issues with the current component:
It might be worth considering a rework of the ErrorPage component and adopting it as a single generic solution for displaying error pages (or sections) across all MFEs.
Some additional context