Next.js Storefront: GraphQL Codegen, TypeScript & TypedDocumentString

Подписаться 18 тыс.

Просмотров 3,9 тыс.

50% 1

GraphQL Code Generator is a robust development tool that automates the generation of code from your GraphQL schema and operations. By creating strongly-typed code in a variety of languages, catching errors at compile time, it boosts productivity and reduces errors. With its customizable and pluggable nature, it caters to a wide range of use-cases, supporting anything from TypeScript typings to React Hooks, Apollo Client code, and more. This tool offers seamless integration with existing schema and promotes consistency, efficiency, and improved overall development experience.
In this video we will be using newly introduced TypedDocumentString for automatically enhancing our GraphQL operations with TypeScript types when fetching data from our GraphQL API.
#nextjs #graphql #typescript

Опубликовано:

3 окт 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 15

@stevenbaron358 Год назад

These series are great! thank you, guys. where is the next one!? :)

@nvcodes Год назад

This was exactly what I was looking for!!! Thank you for your help. Looking forward to more of your videos :)

@NimeshkaSrimal Год назад

great video. looking forward for the next one!

@Juaaanse Год назад

When's the next episode going live? This series is awesome 👏

@ChristopherBenko 9 месяцев назад

Hey, really enjoyed video 1 & 2, but cant seem to find the next videos was this project abandoned?

@hazemturki 8 месяцев назад

Source code?

@pawel_890 Год назад

It don't like this approach. Now you have a lot of boilerplate code, Types are not automated, and there are casting of types.

@zaisteprogramming Год назад

Interesting! Could you elaborate? From my perspective we have just GraphQL files that we need to define the shape of responses (only queries so far) and the `execute` that connects it, the rest is generated and I wouldn't call it boilerplate. Still, there are a few improvements we are going to make here.

@typeofweb Год назад

Quite the contrary! Types are automatically inferred based on the TypedDocumentNode or TypedDocumentString :) If you dislike using fetch directly (the part that you called "boilerplate") and don't mind adding a dependency, you can try using `graphql-request` instead. However, I highly recommend sticking to bare `fetch` as it really makes it easier to pass next-specific options to it :)

@pawel_890 Год назад

@@zaisteprogramming There is a lot of boilerplate code in the 19:19 - the execute function has a lot of "dependencies logic", and when I as saw casting as GraphlQLResponse... ech