graphql/yoga-server/tutorial/basic/11-summary

[giscus[bot]]

graphql/yoga-server/tutorial/basic/11-summary

GraphQL Yoga Documentation

https://the-guild.dev/graphql/yoga-server/tutorial/basic/11-summary

[zakmayfield]

this was a killer tutorial, props to the author 👏

[Akemine]

True.

[jackmacaa]

I have finished the basic section and went on to add in codegen so I could get types generated for the resolvers.
There were some issues with the prisma types not lining up with the graphql types. E.g. the prisma Date type needs to be converted to a string in the resolver. Also the id type which is a number in prisma doesn't line up with the graphql id type which is string. Is there a way I can get the schemas and the auto types to line up without having to write transform functions in the resolvers?

There was also some confusion with the types for Comments inside of the Link type. The prisma context link model didn't return comment[] in the types, but it actually is returning at run time. I had to create a transform function that added in "comment": [] to the Link type to make the resolver return type happy. This worked but it was confusing in reality since this empty array is being overwritten by the Link sub resolver and did actually return the comments.
Thanks, great tutorial. I have only used yoga with 3rd party APIs before, I had never done it with my own DB, it's great writing the same schema for both and it just working. The fact the types didn't line up in the resolvers though was annoying.

[lavet13]

Yes you could solve it by using mappers in graphql-codegen, here is what I came up with:

import { CodegenConfig } from '@graphql-codegen/cli';

const config: CodegenConfig = {
  schema: './src/graphql/types',
  emitLegacyCommonJSImports: false,
  generates: {
    './src/graphql/__generated__/types.ts': {
      plugins: ['typescript', 'typescript-resolvers'],
      config: {
        useIndexSignature: true,
        contextType: '../../main#ContextValue',
      },
    },
  },

  config: {
    mappers: {
      Link: '../../../node_modules/.prisma/client#Link as LinkModel',
      Comment: '../../../node_modules/.prisma/client#Comment as CommentModel',
    },
    inputMaybeValue: 'undefined | T',
  },

  watch: true,
};

export default config;

[jackmacaa]

Ah great thanks ill take a look at that.
I have also noticed there is a way to create the Date type inside of the GraphQL schema by creating a custom Scalar https://the-guild.dev/graphql/tools/docs/scalars. It would be good to know what the preferred approach is here.