Setting up "Models" section about ktor-openapi-generator HOT 8 CLOSED

@SerVB I changed the model acquisition system in the new release. Please verify if your issue persists or not.

from ktor-openapi-generator.

Hi, Generics classes are unsupported.
Reflection is used during initialization, and generic types are erased. See JVM type erasure. This is one of the biggest caveats of JVM languages...
One way around it is to wrap your generic types like this:

class NotGeneric: GenericClass<Generic>()

This should allow the reflection to find the appropriate types.

from ktor-openapi-generator.

As for the nulls, the library currently relies on ktor to serialize the model into json. The mapper.setSerializationInclusion(Include.NON_NULL) should be activated for Jackson.

from ktor-openapi-generator.

Although thinking about it, the KType information seems to have the generic information... Maybe there is a way to handle it.

from ktor-openapi-generator.

Also, there is a hook in the configuration that allows you to properly rename the classes to be digestible by the standard.

from ktor-openapi-generator.

https://github.com/papsign/Ktor-OpenAPI-Generator/releases/tag/0.1-beta.1

Fixed. Marking as closed.

from ktor-openapi-generator.

@Wicpar, thank you! I see many changes, for example, T and kotlin.collections.List have disappeared.

However, there are things that I still don't understand:

3. minimum: null/maximum: null for string and boolean seem redundant.

If I do mapper.setSerializationInclusion(Include.NON_NULL), these redundant lines disappear but it's not a solution, because also my server stops sending fields with null values. I want it to continue sending objects like {"data": null}.

4. minimum: -2147483648 for id: int32 isn't appropriate, I want it to start with 0.

So is there a way to annotate it?

from ktor-openapi-generator.

these are separate issues...
Currently the model is made with data classes and serialised from it. I'll have to change the whole model system to make it work like that. This can be quick fixed with a separate object mapper that serialises it to string in the openapi.json endpoint.
Also, currently there are no @min @max annotations. Though it can be added quite rapidly iirc.

from ktor-openapi-generator.