leecade / leecade/react-native-practice
Use `context` instead of passing props to deep components
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 8
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
https://facebook.github.io/react/blog/2014/03/28/the-road-to-1.0.html#context
It's looks like a global variable, every child components may read it.
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are named. Start by reading the linked React context article and locating components that pass props through multiple levels; confirm the intended scope and acceptance criteria before changing anything. Done means the identified deep prop chain uses context without breaking affected component behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, react-native
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100