graphprotocol / graphprotocol/indexer
Use GraphQL codegen server preset
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 262
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
Today for the GraphQL API if we want to add a new operation we have to write SDL, manually update the types and then write resolvers. We can simplify this process using GraphQL Codegen server preset. It would be taking the work from my refactor started here https://github.com/graphprotocol/indexer/pull/859 and only to be done after #960
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 by reviewing the GraphQL Codegen server preset documentation and the refactor in PR #859, after confirming that issue #960 is complete. Trace how the GraphQL API currently defines SDL, types, and resolvers. Done means new operations can use the server preset without manually maintaining generated types, with existing API behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, typescript
- Domain
- api, backend-api-design
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100