graphprotocol / graphprotocol/indexer
use `@whatwg-node/fetch` and remove all other clients
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 262
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
Today we are using axios, isomorphic-fetch and even built in fetch. We should refactor all these and utilize @whatwg-node/fetch for consistency. In graph-tooling we create a wrapper around @whatwg-node/fetch and provide a shared headers which is a good practice.
You can learn here why use @whatwg-node/fetch
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 points to graph-tooling's packages/cli/src/fetch.ts wrapper; read that example and the linked rationale first. Then inventory axios, isomorphic-fetch, and built-in fetch usage in the indexer. Done means all clients consistently use @whatwg-node/fetch, but the issue names no indexer files or tests, so locating affected entry points is part of the work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100