Feature request: use idiomatic gRPC endpoint URLs

Currently, when defining:

package com.example.ns {
  @outputPackage("com.example.grpcns")
  object protocol {
    // ...
    @service(Protobuf) {
    trait MyService[F[_]] {
      def myMethod(request: MyRequest): F[MyResponse]
    }
  }
}

the idlGen command produces idiomatic gRPC code:

// ...
package com.example.grpcns;
// ...
service MyService {
  rpc MyMethod (MyRequest) returns (MyResponse);
}

When using protoc to generate client code for this, the client calls com.example.grpcns.MyService/MyMethod as expected:

• with namespace
• with UpperCamelCase method name

But the Mu server will only accept MyService/myMethod calls:

• without a namespace
• with lowerCamelCase method name

This seems to be non-idiomatic gRPC usage and breaks compatibility with IDL-generated clients.

Suggestions for the served gRPC endpoint URLs:

1. Use the @outputPackage annotation to define the namespace.
2. Capitalize the first letter of the method name.

Example project:

• https://github.com/sander/rpctest/tree/f45616a720091d88c06d0a5be00f5a2f4306f7aa doesn’t work, since the Go client tried to reach a prefixed and UpperCamelCase method
• https://github.com/sander/rpctest/tree/e018d5e5d1812b107d976aa7bbfb6617c223c761 does work, but now there is no namespace support and I needed to write UpperCamelCase in Scala which seems un-idiomatic

[fedefernandez]

@sander thanks again for your feedback. This issue has been accomplished in #622 and released with the 0.18.4 version (it’ll reach maven central soon)

Now you can set the idlGenIdiomaticEndpoints setting key to true for generating scala service definitions that will append the namespace to the operations and their names will be capitalized.

[fedefernandez]

@sander we have added a couple of parameters to the @service annotation for controlling the service prefix and method name case. I’ve created a PR in your demo project to show how to configure it.

We’re planning to add a new setting key to the idl plugin for controlling that when converting from avdl or proto to scala and update the docs. Once these two tasks are done, we’ll release a new version.