Seeking Codegen feedback

I’d like to remove codegen completely in an upcoming major release of the CLI. For awhile, graphql-code-generator has been a superior tool which offers compatibility with all of Apollo’s tools. We highly recommend migrating to it.

For anyone who is still using Apollo’s codegen feature, is there anything in particular that’s prevented you from making the switch?

[markhalonen]

can you share your use-case for accessing intermediate types?

For example I’d import a type such as

import {
PartNumberProcessQuery_partNumberById_processNodeByDefaultProcessNodeId_descendantRelationships_processNodeByFromId as ProcessNodeWithDetails,
} from '../generated'

and then parse a tree into an ordered flat list of these Nodes, and then pass that flat list to a child component.

ad-hoc lookup types should solve that for you

Ah, I looked that up. I’ve never used lookup types before. Wow, TypeScript is powerful! That would be a solution for intermediate types.

Well, especially with the Apollo maintainers advocating for graphql-code-generator it seems a migration is in my future… Thanks for the tips guys!

[trevor-scheer]

@dotansimha thanks for that fantastic writeup, I’m sorry we never went forward with any of the suggestions you laid out. It certainly wasn’t for a lack of effort on your part - as I’m sure you can tell this repo has gone unloved for some time now. 2 years ago, the idea of wrapping graphql-code-generator might’ve been appealing, but at this point we’re actively trying to push users away from the CLI (in most cases, when possible, excluding a few client:* commands which aren’t yet supported by rover).

I’m going to leave #2053 open for now since there’s a lot of great information there for people looking to migrate, in hopes that it’s slightly more discoverable open instead of closed. You’re more than welcome to close it if you choose, I’ll probably close whenever I finally get to cut the last major for these packages.