MetaMask / MetaMask/eslint-config
Prevent the use of `any`
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 12
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
These lint rules would help prevent the use of `any`:
```
'@typescript-eslint/no-unsafe-argument': 'off',
'@typescript-eslint/no-unsafe-assignment': 'off',
'@typescript-eslint/no-unsafe-call': 'off',
'@typescript-eslint/no-unsafe-member-access': 'off',
'@typescript-eslint/no-unsafe-return': 'off',
```
We should consider enabling them to improve type safety.
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
Start at the shared ESLint configuration entry point and inspect how the listed @typescript-eslint rules are currently configured. Determine the impact of enabling all five rules, then verify the configuration with the repository's available checks; done means the rules are enabled without breaking the config.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100