Real types, with autogenerated names that aren’t possible to reference unless using escaped identifiers (a reminder that you should probably break it out to a real type definition if you want to reuse it).
One could also imagining supporting the attribute to set the name for a generated type:@as
I think it’s right that reuse is explicit. What case does the @as addition proposal needed specifically?
It reminds me of the exportFragmentSpreadSubTypes option in the GraphQL code generator. It was quickly abused at scale, so it had to be disabled.
