openedx / openedx/frontend-platform
Adopt ErrorPage from frontend-platform as the standard for MFEs
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 91
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with src/react/ErrorPage.jsx in frontend-platform, then review the custom ErrorPage implementations found through the linked Open edX code search and the frontend-app-catalog discussion. Identify the flexibility, visual, and message gaps before proposing a shared standard. Done would mean an agreed ErrorPage design suitable for page content or sections and a path for MFE adoption.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100