Some thoughts compared to graphqlgen

So I just tried out https://github.com/prisma/graphqlgen and this library with the following template: graphql-codegen-typescript-template to create Typescript types for resolvers.

I wanted to give some feedback on some things I liked better about graphqlgen.

1. If a query/mutation doesn’t have any arguments, graphqlgen generates the args Typescript type as {} which I like better than the template which uses any.

2. graphqlgen let’s me set what the Context type is upfront, so I don’t have to do QueryResolvers.Resolvers<Context>, I can just do QueryResolvers.Resolvers.

3. I’m not sure how to handle this case:

So my schema is this:

type Post {
  id: ID!
  title: String!
  content: String!
  published: Boolean!
  author: User!
}

type User {
  id: ID!
  name: String
}

type Query {
  post(id: ID!): Post
}

So in the post resolver it expects me to return an author, but I really want to return a authorId and have the Post.author resolver use the authorId to fetch and return an author. graphqlgen solves this by allowing you to create your own typescript types and it will use those.

[kamilkisiela]

Hi @benawad

1. it’s something we can fix asap.
2. It’s is not implemented but we can do it 😃
3. it’s possible, you can overwrite all: parent, context, returned value.

Each field has it’s own type that looks like this:

export type PostResolver<R = Post | null, Parent = any, Context = any> = Resolver<R, Parent, Context>;

So you can:

const postResolver: PostResolver<string>;

[dotansimha]

@benawad If you are using dataloader to batch requests then it’s great 😃 Then your resolver should expect to get then full object and not just the id, but the linked resolvers should return string in order to fetch it from the dataloader.

Then you should be able to use the generics to override the return value of each resolver, and set it to string. And with the latest version you can override the Parent value (using generics).

Also, @kamilkisiela added a mappers features in this PR, so now you can also custom mapping between GraphQL types and TypeScript interfaces, and this way it will override it in the whole generated file (and then you don’t have to use generics each time).