Tracking issue: gql.tada

[phryneas]

We want to evaluate gql.tada and see how it fits into our recommendation.

In this tracking issue, we'll collect findings.

[phryneas]

My current line of thinking (definitely not finalized):

gql.tada could be a part of our recommended pipeline in companionship with graphql-codegen (for possibleTypes), potential bundler extensions, and our own VSCode Extension.

For people who do not use VSCode (vim or WebStorm users), we could go one step further and recommend the GraphQLSP in conjunction.
For people who write their GraphQL documents in separate gql files or just use different languages than TypeScript altogether, we would still recommend graphql-codegen for type and code generation in combination with the VSCode Extension.

There are a few open questions I'm going to collect here as well:

• Fragment story. The "classic" fragment story seems covered by gql.tada, but I'm not so sure about globally registered fragments with our FragmentRegistry.

[sayandedotcom]

any update on this, at first it was working but now it isn't.

[kyrylofranko]

@sayandedotcom just curios what exactly doesn't work for you - querying fragments with gql.tada with Apollo client 3 with possibleTypes set?