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
We certainly can see the benefits of the more idiomatic Kotlin projections and find it makes our client queries more manageable.
However, the "experimental" status in the documentation could cause some client concern.
Questions: Is the new Codegen API still considered "experimental" from a maintainer perspective? If so, is there a roadmap to making it non-experimental?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
A team I work on has been investigating the possible usage of the "experimental" Kotlin Codegen APIs (here: https://netflix.github.io/dgs/advanced/kotlin-codegen/) for use on a client project.
We certainly can see the benefits of the more idiomatic Kotlin projections and find it makes our client queries more manageable.
However, the "experimental" status in the documentation could cause some client concern.
Questions: Is the new Codegen API still considered "experimental" from a maintainer perspective? If so, is there a roadmap to making it non-experimental?
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions