Support Codegen of Operations without Response Models

[Iron-Ham]

Use case

I would like to be able to generate the operations independent of the response models, such that the response models (initially) return a JSON dictionary.

Describe the solution you'd like

No response

[calvincestari]

@Iron-Ham are you still wanting the type-safe parsing of the GraphQL executor? If so then would simply exposing the raw JSON response suffice?

[Iron-Ham]

I filled out a pretty sparse issue here -- so perhaps I can help illuminate my use-case and my thoughts:

Since we have to support n schemas, where n-1 schemas are a snapshot of our live schema, we end up generating n operations and response models (we don't want to request properties or send inputs that don't exist on a given schema version). Then, we separately generate an interface over each of these models and operations. But the more versions that we support, the larger the mass of generated code we have in our binary.

My thought:

In effect, we are associating a new (Apollo codegen flavored) model with n operations. Could we cut out the generation of the n response models, and instead just generate one set of response models that we can then associate to our operations? That association doesn't have to be done automatically -- since they can be instantiated via JSON, we can just one-line it ourselves.

The concern is basically being able to cut down on our binary.

[alex-king-ck]

We could potentially use this functionality as well, but we'd still want models generated at the top level, and the ability to skip code generation on a subset of an operation's query if possible.