feat(#389): allow templating for generated Java / Kotlin class names

[BlasiusSecundus]

Adds an optional nameTemplate input parameter to the plugin, allowing customization of the generated Java / Kotlin class names.

The following template variables are supported:

• name - the original name of the class
• schemaType - the GraphQL schema type (Type, Input, Interface, Enum)

The default value for this new property is null. In this case the output will be identical to the current one.

Examples:

Given an original class name Person and schema type Type:

• null -> Person
• "{name}GraphQL{schemaType}" -> PersonGraphQLType
• "{name}GraphQL" -> PersonGraphQL
• "{name}{schemaType}" -> PersonType

[congotej]

Hi @BlasiusSecundus! Thank you for opening this PR, I am actively looking into this. In the meantime, could you please resolve the conflicts?

[BlasiusSecundus]

I have resolved conflicts. However, when running the tests locally I saw KotlinCodeGenTest failing with errors like this one:

error: unresolved reference: fasterxml
import com.fasterxml.jackson.`annotation`.JsonProperty
           ^
error: cannot access built-in declaration 'kotlin.String'. Ensure that you have a dependency on the Kotlin standard library
import kotlin.String

I have not noticed this before, and this also happens on master branch, so I think this should not be related to my PR.

[mfjBiz]

@BlasiusSecundus
Hello, thank you for your work on this PR. We find it to be incredibly valuable for our use case.

Regarding the KotlinCodeGenTest failure you mentioned, I've checked out the latest master branch and it seems that the issue may have been resolved there.

[BlasiusSecundus]

I rebased and resolved the conflicts. The aforementioned error still occurs on my machine (asl on master), but the CI build job ran successfully (on my forked repo at least). So maybe this is something related to my local setup only, I'll check.

[mfjBiz]

@BlasiusSecundus
Thank you for taking the time to rebase and resolve the conflicts. It's good to hear that the CI build job ran successfully on your forked repo.

@congotej
I noticed your previous comment about actively looking into this PR. Could I kindly ask for an update on the current status of this PR?
We're really looking forward to benefiting from this feature. Thank you!

[BlasiusSecundus]

Btw. This PR should also address issue #323