MichalLytek / MichalLytek/typegraphql-prisma
Use graphql-parse-resolve-info instead of graphql-fields
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 918
- Forks
- 130
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the issue**
Package `graphql-fields` is deprecated: https://github.com/robrichard/graphql-fields#deprecation-notice
**Are you able to make a PR that fix this?**
Maybe in the future but for now I lack knowledge for it
**Additional context**
They recommend using [graphql-parse-resolve-info](https://www.npmjs.com/package/graphql-parse-resolve-info) instead: [guthub repo](https://github.com/graphile/graphile-engine/tree/v4/packages/graphql-parse-resolve-info)
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
Search the repository for uses of graphql-fields, then read the graphql-parse-resolve-info documentation and the linked repository to understand the replacement API. Done means the deprecated package and its usages are migrated without changing resolver behavior, with the project's existing checks passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, typescript
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100