Skip to content

Support shared generated classes for gql response types #2133

@mHaney15

Description

@mHaney15

Is your feature request related to a problem? Please describe.
We are using the introspect-schema and generate-client Maven goals to create the POJOs for our GraphQL client. However we have multiple queries/mutations that all use the same types. While there is only one type in the SDL, a class is generated for EACH of the queries we define. These classes are identical except for the package they are defined in and we don't want to handle all the different classes. It makes more sense to just not use the Maven goals and manually write our Response POJOs since we would have to map them all to a common class anyway.

Describe the solution you'd like
Allow the generate-client goal to create shared classes for gql response types like it does for input types so we don't have duplicate classes in the client.

Describe alternatives you've considered
Alternative would be to map all of the response objects to a common classes, but at that point it's just as much work to write our own response type POJOs.

Additional context
I wish I could open issues from my eg internal account :P

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions