Question: Is there any option to skip some fields when generating types?

[klys-equinix]

Specifically, this is important for Child Datafetchers - one might want to retrive only some parent fields in parent resolver, and the rest through child resolvers - but generated parent type will always have the children fields that have separate resolvers.

[jiholee17]

Hi, there's a @skipcodegen directive you can use on specific fields or types in your schema to skip generating code for them:

type Person {
  name: String
  email: String @skipcodegen
}

This would create a Person Java type with a field/setter/getter for name but not for email.
I don't think this is documented anywhere so I'll make a note to add it to the docs.

[klys-equinix]

I also have a followup question - is there any option to generate interfaces instead of classes for selected graphql types (lets say i want to extend them in my code)

[jiholee17]

Yes, you can use the generateInterfaces = true configuration option to generate interfaces for data classes which you can extend. You can find more information along with other config options to customize your codegen in the documentation here.

[klys-equinix]

Also, are you sure this works properly for kotlin? No interfaces generate for me - but i am using a maven integration for your plugin
deweyjose/graphqlcodegen#292

[klys-equinix]

Actually, i have setup a gradle project to verify, and I cannot see any interfaces generated for types if I use

tasks.generateJava {
    schemaPaths = mutableListOf("${projectDir}/src/main/resources/schema")
    packageName = "com.testdgs"
    generateClient = false
    language = "kotlin"
    generateInterfaces = true
}

I am using

    id("com.netflix.dgs.codegen") version "8.1.0"

[klys-equinix]

@jiholee17 is this a bug?

[jiholee17]

You're right that generateInterfaces only applies to generated Java code, not Kotlin. This isn't a bug, it was just never implemented for Kotlin according to this old issue. I'll discuss with the team about re-evaluating adding support for this in Kotlin.

[klys-equinix]

thx

[klys-equinix]

@jiholee17 It seems there is already an old hanging PR for that
#384
can it be reviewed?