graphql-code-generator VS rtk-query-codegen

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

The nice thing is FastAPI generates OpenAPI. And you can use that to generate a fully typed React-Redux-Typescript client https://github.com/rtk-incubator/rtk-query-codegen . So oddly enough it's even faster than code sharing because everything is generated for you, whereas otherwise you could share interfaces but you'd still have to write the client code.

As an example, this is the "boilerplate" for >20 complete api endpoints and hooks for them: https://github.com/rtk-incubator/rtk-query-codegen/blob/next/test/fixtures/generated.ts

But really, that should only be a real concern once you reach 50+ endpoints. If you look at the autogenerated api for the OpenAPI petstore example with somewhere around 20+ endpoints, that's still pretty manageable. (And autogenerated, so nothing to worry about anyways.)

Currently using dtsgenerator but will probably migrate to RTK query codegen soon, neither of which has the functionallity for that.