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
Kotlin input parameters generation does not support useWrapperForNullableInputTypes configuration property (https://github.com/kobylynskyi/graphql-java-codegen/blob/main/src/main/java/com/kobylynskyi/graphql/codegen/kotlin/KotlinGraphQLTypeMapper.java#L193).
Looking at the comments mentioned below I am not sure if adding support for this flag is planned?
Kotlin does not provide org.springframework.graphql.data.ArgumentValue functionality - only kind of an equivalent of the optional pattern. ArgumentValue provides both nullable optional and omitted flag features that could be very useful in input parameters.
The optional specification of Java SE8 is not applicable to scala and kotlin. In the functional programming, the data class has accurately described the data type. Therefore, I think only Java needs it.
I omitted Kotlin, when implementing, because of the above comment, and because there is no build-in wrapper like ArgumentValue to wrap it with.
ArgumentValue is specifically supported in graphql-java project, which means the serializer knows how to handle it. If we make our own, it will not be able to (de)serialize it. So that is not an option.
Kotlin input parameters generation does not support
useWrapperForNullableInputTypes
configuration property (https://github.com/kobylynskyi/graphql-java-codegen/blob/main/src/main/java/com/kobylynskyi/graphql/codegen/kotlin/KotlinGraphQLTypeMapper.java#L193).Looking at the comments mentioned below I am not sure if adding support for this flag is planned?
Kotlin does not provide
org.springframework.graphql.data.ArgumentValue
functionality - only kind of an equivalent of the optional pattern.ArgumentValue
provides both nullable optional and omitted flag features that could be very useful in input parameters.Originally posted by @jxnu-liguobin in #1450 (comment)
The text was updated successfully, but these errors were encountered: