openedx / openedx/frontend-app-authoring
Each Editor should manage its state independently
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 17
- Forks
- 218
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 20
Description
Once https://github.com/openedx/frontend-app-authoring/issues/2091 is complete, for each editor (problem, video, text, etc.) move its redux state into a redux store specific to that editor or (even better) into a React Context specific to that editor.
i.e. don't use one big state in /src/editors/data/redux/index.ts which has video, problem, etc. fields - instead the video editor should have its own videoReduxStore or (better) VideoEditorContext (Redux context).
This is similar in goals to https://github.com/openedx/frontend-app-authoring/issues/1239
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
First review issue 2091 and the existing state in /src/editors/data/redux/index.ts, then compare the goals with issue 1239. Map how the problem, video, text, and other editors currently use the shared state. Done means each editor has its own Redux store or React Context rather than fields in one shared store.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100