Tim Kendall

Right now we default to `unknown` types.

We should run the TypeScript type-checker on the generated output (Prettier already runs the parser). Relates to #46

From the README it is not immediately obvious how to build a type-safe SDK with this library/tool. Perhaps we should implement a separate CLI (`create-graphql-sdk`?) or command that drives this...

https://mikro-orm.io/docs/usage-with-js Relates to #27

Would be nice to publish to GitHub Package Registry as-well-as NPM for redundancy and ease-of-adoption.

- Unwrap `data` object (i.e so we don't have to do `data.hero...`) - HTTP Keep-alive by default - Persisted query support - Structured logging support - Exponential backoff retry -...

https://formidable.com/open-source/urql/docs/

I'm working on a new fluent Graphql Client [timkendall/tql](https://github.com/timkendall/tql) that makes use of [TypeScript 4.1's new sweet Recursive Conditional Types](https://devblogs.microsoft.com/typescript/announcing-typescript-4-1/#recursive-conditional-types) to offer a really sweet (type-safe) DSL for writing arbitrary...

Comparison against alternatives

1

> Might be useful to have a comparison table between this and others, especially [npmjs.com/package/@graphql-codegen/client-preset](https://www.npmjs.com/package/@graphql-codegen/client-preset) which perhaps is the most popular option but suboptimal DevEx This would be good to...

Background (May not be relevant): I have a `Droplet.SingleInput` nested in a `Droplet.Area`. I am hiding the `SingleInput` so I can have a custom styled `input`. I trigger clicks on...