Refactor remaining Redux stores to use React Contexts
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 611
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 49
Description
Pontoon's front-end state management has been a bit messy for a while, as most things (including everything new) uses React contexts, but we still have a bunch of Redux stores maintaining some of the state.
All of the Redux stores should be refactored to use React Context instead, with no user-visible changes.
This work can and should be done in multiple PRs, as the stores are more or less independent of each other.
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 reading translate/src/rootReducer.ts to identify the remaining Redux stores and choose one independent store to migrate. Trace that store's frontend consumers before changing its state mechanism. Done means the selected store uses a React Context, behavior is unchanged for users, and no remaining Redux usage exists for that store.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, redux, typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100