You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, the Kotlin client uses LocalDateTime to represent the date-time received from the server.
This is because because LocalDateTime doesn't have a notion of timezone.
openapi-generator version
4.2.2
Steps to reproduce
Related issues/PRs
Suggest a fix
It would be better to represent the date time received by the server in a OffsetDateTime which contains the timezone information.
The Java generator and the KotlinSpringServer also use the OffsetDateTime.
Description
By default, the Kotlin client uses LocalDateTime to represent the date-time received from the server.
This is because because LocalDateTime doesn't have a notion of timezone.
openapi-generator version
4.2.2
Steps to reproduce
Related issues/PRs
Suggest a fix
It would be better to represent the date time received by the server in a OffsetDateTime which contains the timezone information.
The Java generator and the KotlinSpringServer also use the OffsetDateTime.
openapi-generator/modules/openapi-generator/src/main/java/org/openapitools/codegen/languages/AbstractJavaCodegen.java
Lines 471 to 476 in fb0479a
openapi-generator/modules/openapi-generator/src/main/java/org/openapitools/codegen/languages/KotlinSpringServerCodegen.java
Lines 104 to 107 in fb0479a
The text was updated successfully, but these errors were encountered: