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
At the moment, the documentation contains a non-trivial example for Kotlin, which is a little counterintuitive. I propose the documentation offer "hello world"-style examples that only focus on the specific of setting up Connect in a specific language, leaving more advanced features and use cases in a separate section of the doc.
Also, since Java is still a popular language, and Kotlin is Java compatible, probably it would be great to have a "Getting started with Java" that mentions that the code generated is in Kotlin, and you need a certain setup, but you can use Connect when coding in Java
Hey @edmondop! We intended the Swift and Kotlin implementations to be primarily for mobile developers - that's why they're client-only. Eventually, we'd like to have a full Java implementation. (If you're interested, leave a response on https://github.com/orgs/connectrpc/discussions/11.)
All that said, we should provide a simpler example for server-side Java developers to get started with our Kotlin clients. It probably won't happen soon unless you'd like to open a PR 😉, but we'll get to this eventually!
At the moment, the documentation contains a non-trivial example for Kotlin, which is a little counterintuitive. I propose the documentation offer "hello world"-style examples that only focus on the specific of setting up Connect in a specific language, leaving more advanced features and use cases in a separate section of the doc.
Also, since Java is still a popular language, and Kotlin is Java compatible, probably it would be great to have a "Getting started with Java" that mentions that the code generated is in Kotlin, and you need a certain setup, but you can use Connect when coding in Java
Reference: https://connectrpc.com/docs/kotlin/getting-started/
The text was updated successfully, but these errors were encountered: