Bogdan Kobylynskyi

@JBrVJxsc, it's a good catch. Do you have some expectations on how it should work in such scenarios? btw, if you don't need `toString()`, you can disable it using: `false`

Relevant to rzwitserloot/lombok#2255

@vpandey3 please provide the code that you expect to be generated

Thanks for providing the info. The thing is that you are using query response type as an input, so it is considered as the parametrized input. Try disabling the following...

Overall your schema design looks not as per GraphQL best-practices. I think the better solution would be: ```graphql type Query { productOrganization(id: ID!): ProductOrganization } type ProductOrganization { id: ID!...

I like the idea, but my main concern is how to gracefully manage cross-package imports. Need to think about this a bit more, but in general, the feature request is...

@robbertnoordzij, you can already do that. Check https://github.com/kobylynskyi/graphql-java-codegen/tree/master/plugins/gradle#different-configurations-for-graphql-schemas

I am totally fine with introducing a new config `generateImmutableModels` (default = `false`). The only concern I have is that it is better to keep fields private and to generate...

Hi @chusmc Thanks for providing such detailed information. What if you manually register required modules during the application init/startup phase in the following way: `GraphQLRequestSerializer.OBJECT_MAPPER.registerModule(new SimpleModule().addSerializer(new OffsetTimeSerializer()));` The working test...

@Frederick888 thanks for your feature request. This seems doable by slightly changing serialization logic by: * Removing a null-check in `GraphQLRequestSerializer#buildQuery` * Changing a generated `Builder` class in `QueryRequest` classes...