6/6 rust's graphql tooling is probably good enough for projects where you're defining your own schema and can adjust it to fit well with the tooling.

My experiences with js/ts packages weren't necessarily all that much better. I probably need to adjust my expectations.

5/6 juniper & juniper-from-schema seem pretty much inactive projects.

juniper-from-schema panics when it tries to parse github's schema. I gave up at this point.

4/6 graphql-client needs to generate unique named types throughout the query. This seems reasonable, but type names like ProjectItemsOrganizationProjectV2ItemsNodesContentOnIssueTrackedIssuesNodes are pretty unwieldy.

Maybe I'm holding it wrong?

3/6 graphql-client & spreading:

github accepts this sort of this:

content { ... on Node { id } ... on UniformResourceLocatable { resourcePath } }

graphql-client only accepts the top-level options, so you need something like:

content { ... on DraftIssue { id } ... on Issue { id resourcePath } }

2/6 graphql-client can mostly cope with github's schema and queries I wrote before. However, it needs more explicit __typename's, and is has a stricter view on spreading.

"that's not the gearstick"
"I know"

I almost feel bad for some of them. I think cyber truck preorders started before Elon went off the deep end.