Skip to main content

GraphQL Code Generator 1.5 is out!


I am happy to announce a new version of GraphQL Code Generator!
The new version has plenty of fixes and a lot of new features (you can check out the full changelog here)!
The GraphQL Code Generator is part of a growing number of open-source libraries maintained by The Guild. If you explore those libraries you can see that they have very few issues and are extremely well maintained.
This is due to the unique working model of The Guild and our Connected Build system – a system where some of our users can connect their build pipelines into our libraries and we make sure to keep them updated and working (you can reach out directly if you want to join).

Apollo Federation support

GraphQL Code Generator always supported generating types for the backend resolvers — one of the most used features.
Recently we’ve received a request to support Apollo Federation. We started looking into how we could do that and Kamil Kisielabegan implementing Apollo Federation support into GCG version 1.5 in just a few days!
Now, your Apollo Federation services can have strongly typed resolvers, both in TypeScript and Flow, by simply enabling a flag in your codegen config:
federation: true
In addition to TypeScript and JavaScript, we are also generating outputs for more backend languages, like Java for example. Please reach out if you want to test the generator for those languages as well.

React-Apollo 3.0 Hooks

For a few months now, we not only supported generating fully-typed react-apollo HOC and query components but also supported generating fully typed hooks created by the react-apollo-hooks library.
So it was an easy update for us to support the new react-apollo 3.0 hooks that are based on the react-apollo-hooks library. We’ve also supported the beta versions of react-apollo during their testing period.
Instead of generating just TypeScript types, generate fully typed and ready to use hooks. Save yourself a lot of code and potential mistakes (such as typos or using the wrong interface) and be sure everyone in your team has it all strongly typed.
Read the documentation about those on our website in the react-apollo section and try out our full-stack WhatsApp Clone tutorial!

Using Apollo codegen?

If you are using the Apollo codegen today, migrating to the GraphQL Code Generator is easy.
Our default generation output is different than Apollo’s, but because so many people are migrating to our codegen from Apollo, we’ve created some config flags (near-operation-file, preResolveTypes) to make it easier for people to migrate to the best practice more gradually.
But why would you even want to migrate from the Apollo codegen?
  • GraphQL Code Generator is better maintained, with fewer issues even though we have many more features
  • You can generate types for the frontend and the backend
  • There are dozens of community generators for many languages and different ideas
  • You can generate not only types but fully functional UI components
  • GraphQL Code Generator has an easy to work with plugin system. We see many teams writing their own custom logic, for their product’s needs

Comments

Popular posts from this blog

How to use Ngx-Charts in Angular ?

Charts helps us to visualize large amount of data in an easy to understand and interactive way. This helps businesses to grow more by taking important decisions from the data. For example, e-commerce can have charts or reports for product sales, with various categories like product type, year, etc. In angular, we have various charting libraries to create charts.  Ngx-charts  is one of them. Check out the list of  best angular chart libraries .  In this article, we will see data visualization with ngx-charts and how to use ngx-charts in angular application ? We will see, How to install ngx-charts in angular ? Create a vertical bar chart Create a pie chart, advanced pie chart and pie chart grid Introduction ngx-charts  is an open-source and declarative charting framework for angular2+. It is maintained by  Swimlane . It is using Angular to render and animate the SVG elements with all of its binding and speed goodness and uses d3 for the excellent math functio...

Understand Angular’s forRoot and forChild

  forRoot   /   forChild   is a pattern for singleton services that most of us know from routing. Routing is actually the main use case for it and as it is not commonly used outside of it, I wouldn’t be surprised if most Angular developers haven’t given it a second thought. However, as the official Angular documentation puts it: “Understanding how  forRoot()  works to make sure a service is a singleton will inform your development at a deeper level.” So let’s go. Providers & Injectors Angular comes with a dependency injection (DI) mechanism. When a component depends on a service, you don’t manually create an instance of the service. You  inject  the service and the dependency injection system takes care of providing an instance. import { Component, OnInit } from '@angular/core'; import { TestService } from 'src/app/services/test.service'; @Component({ selector: 'app-test', templateUrl: './test.component.html', styleUrls: ['./test.compon...

How to solve Puppeteer TimeoutError: Navigation timeout of 30000 ms exceeded

During the automation of multiple tasks on my job and personal projects, i decided to move on  Puppeteer  instead of the old school PhantomJS. One of the most usual problems with pages that contain a lot of content, because of the ads, images etc. is the load time, an exception is thrown (specifically the TimeoutError) after a page takes more than 30000ms (30 seconds) to load totally. To solve this problem, you will have 2 options, either to increase this timeout in the configuration or remove it at all. Personally, i prefer to remove the limit as i know that the pages that i work with will end up loading someday. In this article, i'll explain you briefly 2 ways to bypass this limitation. A. Globally on the tab The option that i prefer, as i browse multiple pages in the same tab, is to remove the timeout limit on the tab that i use to browse. For example, to remove the limit you should add: await page . setDefaultNavigationTimeout ( 0 ) ;  COPY SNIPPET The setDefaultNav...