Option to generate separate types that are reused

Is your feature request related to a problem?

I'm currently using StrawberryShake to retrieve data from a GraphQL endpoint, than map it to another object model, serialize it to XML to provide it to another service.

The object model and the query response contain quite a few types that are reused on several levels in the object model.
But StrawBerryShake generated the type names in a hierarchical way. Like IMyQueryName_RootObject_ChildObject.
This makes IMyQueryName_RootObject_ChildObject and IMyQueryName_RootObject_OtherNode_ChildObject two different types, although they are the same.

This causes my mapping to require more duplicate methods that only differ in incoming type name.

The solution you'd like

I know this hierarchical way of generating type names is safer to prevent type clashes.

That's why I would like to see the option to generate types in a way that types with the same name are considered the same.
So they are reused in the generated client code.

So I have an easier time mapping.

Product

Strawberry Shake

No files or tests are named. Start by locating Strawberry Shake's generated-client type naming and reuse logic, then determine how an opt-in same-name policy should handle type clashes; done means reused types are generated where names match without unsafe collisions.