darvld / krpc Goto Github PK

The current implementation will fail to generate services with methods using generic types (other than Flow with T being non-generic).

To fix this, the generated Marshaller instances must be obtained differently when the type is generic (add a new method to SerializationProvider).

Allow the users to generate only certain components or exclude them using KSP options. Some examples:

• -client: Generate only client implementation (includes descriptor)
• -strict: Generate strictly the specified components (when using -client descriptor will not be generated)

Currently, enabling KSP's incremental setting causes the compiler to stop geneating code. We need proper support for incremental processing.

Currently, @UnaryCall and @ServerStream calls must have only one argument (the request). We can add support for multiple arguments by wrapping them in a generated data class.

There are currently no tests at all. We need to completely test the processor and the runtime before we can call this a serious project.

The lates KSP release introduced experimental multiplatform support (except for Kotlin/Native). We could try to add it as well, since the final goal is to create a Kotlin Multiplatform implementation of gRPC.

Currently request and response types not marked as @Serializable will raise a runtime error. Is there a way to check this in the compiler?

Both client and server implementations should provide suspending shutdown() and join() method families to allow for a more idiomatic way of closing their channels. Right now it must be done manually by calling shutdown() and yielding until isTerminated returns true.