MichalLytek / MichalLytek/type-graphql
Versioning resolvers
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8.1k
- Forks
- 672
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
Managing change within a schema over time. Schema evolution is a common pattern that is used. But creates complications and headaches of inventing new names or introducing `FieldV2` issues.
**Describe the solution you'd like**
This blog article has an interesting take on managing schemas by dynamically matching resolvers.
https://blog.logrocket.com/versioning-fields-graphql/
It would be great to see type-graphql have an opinionated approach on schema evolution.
**Describe alternatives you've considered**
v2 all the things?
**Additional context**
Naming things is hard, naming them twice is harder.
Contributor guide
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 reading the linked article and reviewing type-graphql's existing schema and resolver APIs. Define the supported schema-evolution behavior and its scope before identifying implementation entry points and tests. Done means the project has a documented, agreed approach with corresponding coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, typescript
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100