[react-native] Migrate off of old context APIs
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- react-native
- Domain
- mobile
Research direction
Start by reading the linked React Native issue (facebook/react-native#28103) to identify the affected code, migration requirements, and tests. The issue is complete when the old context APIs are no longer used and the relevant React Native tests pass.
Written by the indexing model from the issue text.
Description
- Dominant language
- No language data
- Stars
- 126
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
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.
More from callstack/react-native-open-source-board
-
Feature 🛠
Difficulty 4/5 3-5 days Newbie friendliness 20/100
callstack/react-native-open-source-board#264 · 2 reactions ·
-
Feature 🛠
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Feature 🛠 iOS
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Android Bug 🐛
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Automation Feature 🛠
Difficulty 4/5 3-5 days Newbie friendliness 20/100
All issues in callstack/react-native-open-source-board
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nightscout/nocturne#1425 ·
-
ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Bug Flutter User Feedbacks
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
getsentry/sentry-dart#4042 · 1 comment ·