TypeScript codegen

We could generate TS types for the GraphQL queries in the project in parallel of something like graphql-document-collector to get the query docs globally.

I’ll work on this in a folder parallel to the swift/ folder.

[davidyaha]

Yep cool! Would love to see both of these tools actually. Writing typings for objects created from graphql is driving me crazy… 😃

[rricard]

@davidyaha exactly. Right now, my main focus is client-side developer experience. Client side is usually harder and more error prone than client side in my own experience. This is still very much true with GraphQL where creating the schema is relatively easy but building a large app with large queries and such can become incrementally complex.

In the latest example you gave, to me, NestedObj may not require every field the type allows it to contain (see my example). However, NestedObjFragment can be a thing. My point is: here we’re going to be query-based, because that would help with the client DX. However, and I’m glad you brought that up, gql2ts is an amazing tool for server side! Because on the server you can virtually think that everything your schema is providing is immediately available. By the way, I would love having a gql2ts-kind of project available for flow as well!

This is some great stuff discussed here, I don’t think there will be one unique build tool for all of this but a bunch of complementary ones! (in a truly JS-fatigue manner, we’ll figure out later how we’ll make that work for beginners, let’s just start by experimenting!)