Customised toString() function

[medha-kb]

Hello,

I am using the graphql-java-codegen plugin for generating Kotlin classes from a GraphQL schema. I am looking for a way to modify the toString method in the generated classes to include custom logging.

data class Book(val id: String, val title: String) {
override fun toString(): String {
val stringRepresentation = "Book(id=$id, title=$title)"
// logging
log.info("Book toString called: $stringRepresentation")
return stringRepresentation
}
}

Is there a way that allows this level of customization in the generated Kotlin classes via custom templates or some other configuration option? Or would you recommend an alternative approach to customize the behavior of methods in the generated classes?

Any guidance or suggestions on this would be greatly appreciated.

Thank you!

[kobylynskyi]

Thanks for the interest in the library.
Currently we don't support customizing generated methods.

[kobylynskyi]

@medha-kb please share your plugin configuration options, along with a path to the template. Thanks

[medha-kb]

Thank you for your response. Due to confidentiality reasons, I'm unable to share complete configuration details. However, I've added a new section for the custom template under the tag, similar to:

```

<customTemplates>
    <type>path/to/custom_type.ftl</type>
</customTemplates>


This path is adjusted to fit our project's directory structure. Also, could you advise on the recommended version of the plugin for optimal support of custom templates?

[kobylynskyi]

First of, try changing the type to uppercase: TYPE.
Also look at the following related issues:

#1244

#1158

Maybe you might need to supply a customTepmplatesRoot parameter.
Hope that helps.

[medha-kb]

Thank you, I will try the solutions suggested.

[medha-kb]

The custom template works now with the addition of customTemplatesRoot parameter.

However, we have a dependency on another service that is still using an older version of the plugin, specifically v4.1.x
I am interested in knowing if these two versions are compatible with each other. The primary concern is to ensure that the project can continue to work smoothly while using the latest version of the plugin, even though one of our dependencies is on an older version.