above now :). I can do it again. Zeus allows you to generate client library from schema - not from queries. Then you can write queries in TS, you will receive:
- typed args
- typed response
It also offers selectors from which you can create typings for your response objects if you are persisting those somewhere in state, so yeah it is a game changer not only for GraphQL, but for communication with backend and Frontend developer experience.
To be honest it has also some cons, for example:
- variables are custom implementation and don't have typings as for now
- some edge cases are not supported yet
I plan to integrate urql. I generate the whole lib with complicated generic types, so you don't have to write gql queries and run codegen. Just generate once and write interactive queries. No watching and stuff
Why I am posting this? 2 reasons: GraphQL Zeus reached 4.0 and is compatible with huuge schemas, second reason I received a great contribution with full readme rewrite and I packaged it into docs site
We are just running blog. We are experts in the field of GraphQL. We are 2 devs and 2 marketing working on editor after our work. We don't have time to spam. So why do you consider editor a spam?
My name is Artur Czemiel. Tell me your name if you want to accuse me for something that's illegal.
