Is there a way to separate the protoc-gen-go-grpc code and protoc-gen-go code's directory(=package) ?

[take]

Hi thanks for the awesome library!

I'm trying to implement a system using grpc + layered architecture and it would be awesome if I can execute the following command

$   protoc --go_out=./domain/models/grpc --go_opt=paths=source_relative \
           --go-grpc_out=./infra/external_api/grpc_gen --go-grpc_opt=paths=source_relative \
           --proto_path=./proto

usually we pass the same value to --go_out and --go-grpc_out, but since

• --go_out generates messages/serialization
• --go-grpc_out generates the implementation of the server/client

it would be awesome to generate those code to a different layer(directory)

Although if I execute the command above, build will fail since the generated code in the implementation of client/server does not import the messages/serialization properly.

Is there a way to solve this problem?(e.g. pass and import option to the --go-grpc_opt command so the generated code will import the message/serialization properly)

Or we always have to pass the same value to --go_out and --go-grpc_out no matter what?

Thanks,

[take]

I'm sorry this was possible if I set the go_package option correctly