GrpcClient.Builder's baseUrl path segments get ignored

[MariusVolkhart]

When using the compiler to generate a Kotlin client, the GrpcMethod.paths that are generated are absolute. For example /greeter.HelloService/SayHello. The GrpcClient.Builder takes a baseUrl, but since the paths are absolute, and path segments of the baseUrl are discarded when GrpcClient#newCall runs.

If the paths were relative, greeter.HelloService/SayHello (no leading slash), then the baseUrl containing path segments would work fine.

My use case is that I'm adding gRPC to an existing application, and am being asked to deploy it at a path like /appName/grpc/*.

My workaround is an OkHttp interceptor that rewrites the request URL to include the path components I need.

[MariusVolkhart]

I can make a PR with whatever changes, if any, are desired.

[oldergod]

Thanks for reporting. PR welcome !

[swankjesse]

Is this layering with a path prefix something gRPC does elsewhere? I’m unfamiliar with it!