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
common Kotlin and Java types like String, Map, etc. don't need to include the package name
More complex cases like Type<Type1<Type2>>, Type<*> or Type<out Type1> aren't covered. They would need a more advanced Kotlin/Java parser (maybe that could make a nice contribution to KotlinPoet/JavaPoet?).
Right now, we can map custom scalars to Kotlin classes using a Gradle configuration:
This doesn't work anymore with generic types:
One simple workaround is to use a type alias:
But that's adding a level of indirection. Is there value in adding generics support?
The text was updated successfully, but these errors were encountered: