openedx / openedx/frontend-platform
Move shared utility functions to frontend-platform for reuse across MFEs
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 91
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
Description
Currently, we have a set of useful utility functions being used in both the Learner Dashboard MFE and the Catalog MFE. It would be good to consider moving these functions into the frontend-platform repository so they can be reused across MFEs.
[!NOTE]
At the time of creating this issue, the example usage of these functions in frontend-app-catalog is located in the RaccoonGang fork of the repository, but this code will be merged into the upstream repository’s master branch.
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 by comparing the utility usage in frontend-app-learner-dashboard's src/data/services/lms/urls.js and frontend-app-catalog's src/utils.ts. Identify which functions are shared, then inspect frontend-platform's existing structure and conventions for exposing reusable utilities. Done means the shared functions are available from frontend-platform for reuse across the MFEs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100