graphqlgen
graphqlgen copied to clipboard
⚙️ Generate type-safe resolvers based upon your GraphQL Schema
Given a schema: ``` type Subscription { status(acdEngineId: Int!): JobStatus! } type JobStatus { jobStatus: String! } ``` and types: ``` export interface JobStatus { jobStatus: string; } ``` The...
## Description Currently, I found we could not use types imported from other files in the model file. For example, if I have two typescript files like this: ```ts //...
## Description There is flow error in graphqlgen.js after running graphqlgen. I am using custom input type for query and generated interface for it does not contain prefix `Query_`. ...
## Description When the return type is [String]! in schema the generated resolver return type is incompatible ## Steps to reproduce Schema: ``` type Episode { directors: [String]! guestStars: [String]!...
## Description Is this expected behavior? The library was recommended by a Prisma team member as a solution to the need of manually defining resolvers for all relation fields (even...
## Description Does not seem to work with the graphql typescript-advanced project created by graphql-cli: ``` graphql create my-app --boilerplate typescript-advanced ``` ## Expected results Generation finishes without errors. ##...
There is a similar issue to the #15, but when using `mergeSchemas`. The resolvers type expected in `mergeSchemas` is `IResolversParameter` instead of `IResolver`. I guess a similar workaround could be...
**EDIT:** This issue was actually happening with version `0.4.0` which I was unknowingly executing with `graphqlgen` (global install), and realised when I did `npx graphqlgen`. [Actual issue as the subject...
My `schema.graphql` contains: ``` type Post { id: ID! title: String! content: String! comments: [Comment!] user: User! } ``` When I generate the types the suggested type for Post is:...
GraphQL uses `iterall` and supports `Iterable` return values. This PR changes all return types to be iterable and keeps input types as arrays.