Get rid of react-native-i18n
Open
- Dominant language
- JavaScript
- Stars
- 4.8k
- Forks
- 771
- PR merge metrics
- No merged PRs in 30d
Description
Once #777 is merged, react-native-i18n will become almost unused.
The only two things it's used for will be:
* Retrieve the current locale (functionality provided by react-native-device-info)
* Lookup translations strings (easily doable in `t()`
Getting rid of it would mean having 100% control about how our translations are handled in our code.
Opinions?
Contributor guide
Research direction
Start by checking the two remaining react-native-i18n uses described in the issue: current-locale retrieval and translation lookup in t(). Review #777 and the existing react-native-device-info integration before deciding how the dependency can be removed; done means both behaviors remain available without react-native-i18n.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- internationalization, mobile
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100