Move shared utility functions to frontend-platform for reuse across MFEs

Open
#835 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
frontend

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.

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.

Dominant language
JavaScript
Stars
39
Forks
91
Avg merge
2m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openedx/frontend-platform

All issues in openedx/frontend-platform

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.