graphprotocol / graphprotocol/indexer
Stricter linting rules to disallow `any`
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 262
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
A lot of places in code today are just forcing any types. As a new contributor this makes it hard to follow the code and also can cause un-intentional bugs
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
The issue names no files, lint configuration, tests, or entry points. Start by locating the TypeScript lint configuration and searching the codebase for explicit any types. Done means the stricter rule is enforced and the existing violations are addressed without leaving the project unable to lint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100