graphql-code-generator VS graphql-typed-document-node

The @graphql-codegen library is a bridge between your GraphQL schema and the actual code you write. It automates the generation of boilerplate code, ensuring that your data fetching layer is always up to date with your content structure.

In typescript and typescript-resolvers plugin v4.0.1, we have reverted the default ID Scalar input type to string. Read the pull request for more details.

See https://github.com/dotansimha/graphql-code-generator with @graphql-codegen/typescript-graphql-request plugin

Graphql Codegen is a code generation library for GraphQL that enables developers to generate custom code. It provides us developers with the ability to generate type definitions, query builders, documentation, and more by analyzing our GraphQL schemas. This makes it easier and faster to build GraphQL applications and reduces the time spent coding.

It is already incoming, with an example in the repository. 😇 https://github.com/dotansimha/graphql-code-generator/pull/8863

The actual package is @ graphql-codegen/cli

GraphQL Codegen generates frontend types and React hooks from our GraphQL request definitions.

There are two main approaches to keeping the types of the GraphQL schema and entities in business logic in sync. You can generate the schema based on your TypeScript code (e.g. TypeGraphQL), or you can generate types based on your schema (e.g. GraphQL Code Generator). We opted for the latter since it slotted right into our existing GraphQL server implementation using Apollo Server.

For querying in React make sure you use GraphQL code generator https://www.the-guild.dev/graphql/codegen

When using graphql-typed-document-node to generate TS types from gql, I am getting errors when my query has variables.

https://github.com/dotansimha/graphql-typed-document-node

Big thanks to Dotan Simha for creating this TypedDocumentNode!

GraphQL Code Generator can generate fully typed React hooks if you tell it to, but I'm a fan of keeping things simple and thereby of their TypedDocumentNode approach. This variant is unaware of the GraphQL client that you're using. In other words, it's not tied to react-apollo (or alternative).

Hi, I use this package https://github.com/dotansimha/graphql-typed-document-node and I usually call it like this useQuery(peopleDocument, variables).

Controllers are great for lots of reasons. One reason we've found while developing and testing Apollo Elements is that unlike the class-based API of e.g. @apollo-elements/lit-apollo or @apollo-elements/mixins, when using controllers there's no need to pass in type parameters to the host class. By passing a TypedDocumentNode object as the argument to the controller, you'll get that typechecking and autocomplete you know and love in your class template and methods, without awkward class generics.

So today, after successfully integrating this feature into few of our largest clients, we can proudly share it with you - TypedDocumentNode.

Want to generate Typescript objects based on GQL documents? You can try out Typed Document Node