Customizations for @JsonTypeInfo and @JsonSubTypes in generated interfaces about dgs-codegen HOT 4 OPEN

I see, we should be able to fix that, i.e., if given a mapped type config for something that would otherwise be generated, avoid generating that class. I think that is a bug in the current implementation.

from dgs-codegen.

The scenario you describe does seem useful. We'll need to look into whether it is feasible to support. We do have the ability to map types by specifying it in a config in the gradle task. This config handles mapping schema types to Java/Kotlin classes. Might be able to leverage that for generating the @JsonTypeInfo as you mentioned.

from dgs-codegen.

Sorry for the late reply, I just got around to read your reply.

I tried your suggestion and it works quite well (Thanks for that). So i added a mapping for my custom interface "Animal" with necessary @JsonTypeInfo like this:

"Animal" : "de.interhyp.dgs.example.domaingraphserviceexample.animals.Animal"

This works fine, but the only issue is, that the code generator is still generating another interface class with the name "Animal". That a little bit confusing. Is there an option to prevent this?

from dgs-codegen.

I have a similar use case. It would be great if the type info and the sub types could be customized. Much appreciated!

from dgs-codegen.