MetaMask / MetaMask/eslint-config
Create shared React Native config
- Dominant language
- JavaScript
- Stars
- 12
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Once #170 (the shared React config) has been done, we should create `@metamask/eslint-config-react-native`. For the purposes of ESLint configuration, it's useful to think of React Native as a superset of React, which is why we want the shared React config to be created first.
The React Native config should be extended by consumers after extending the base React config.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the shared React config work in issue #170, then inspect how this repository structures shareable ESLint configs. Create the `@metamask/eslint-config-react-native` package so consumers can extend it after the base React config. Done means the React Native config exists with that inheritance relationship.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, javascript, react-native
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100