ScalaPB | Protocol buffer compiler for Scala | Serialization library

You can't completely avoid defining TypeMapper for each enum type you have. But you could create a helper method to create TypeMapper instances.

For example

TL;DR: this is not possible yet as some of the code you are using rely on macros and is not yet published for Scala3.

SBT plugins runs with Scala 2.12 no matter which Scala version is used in your project, thus you don't have to try to use plugins with _2.13 or _3 suffix, just use the regular syntax that will actually pick _2.12 artifacts.

That is, in plugins.sbt:

The ZIO data type is a functional effect. A functional effect is a description of a workflow. This is why we have the run method at the end of the world. This run method executes the provided ZIO effect.

All the rcpMethodN methods are ZIO effect, so they are just a description of running workflow. If you want to run these effects sequentially you should compose them using for-comprehension or flatMap like this:

Firstly, I recommend using Akka gRPC rather than using ScalaPB directly. The documentation is pretty clear and there is a giter8 config that can be used to create a sample project using sbt new.

Secondly, the code in that gitHub does not look like official sample code. It says it has been "translated from grpc java" which is probably not what you want.

Finally, on the specific issue you are seeing, the stubs generated by scalaPB are in a package whose name is given in the proto file. The example file has

Given that you configured your scalabp in sbt as described in installation guide

You need to define a custom type for a field to be converted from int64, mapped by default as Long, into FiniteDuration

For example:

They are temporary files so they are in the target tree in the scala-2.13 directory.

It works as intended. The case class generated has members for each of the fields in the proto. The rest of the generated code takes care of serialization and deserialization. You can read more about the generated code and how to use it here: https://scalapb.github.io/docs/generated-code

To unpack Anys that you don't know their type at compile time, you will need to build a map from typeUrl to the companion object of all the types you might expect, and use that to call unpack. It can be done like this:

I think you want something like this.