Protobuf: modules: how can we use protoc-gen-go now?
Now that Go 1.11 is officially out, I think we should revisit the UX around using protoc-gen-go. How do we deal with not having a GOPATH variable defined? What's now the best way to define an option go_package? How does this change how protoc-gen-go is invoked in the command line?
dchenk
👍2
>All comments
I don't think anything changes.
My recommendation is to always have an option go_package containing the full import path of the Go package in every .proto file, and to always include the paths=source_relative generator option. The former ensures imports of the package use the right import path, and the latter puts your output files where you (probably) expect them.
neild
on 5 Sep 2018
👍4
Was this page helpful?
0 / 5 - 0 ratings
Related issues
junghoahnsc
路
5Comments
parkr
路
5Comments
hxzqlh
路
5Comments
seungryulchoisc
路
3Comments
khadgarmage
路
3Comments
Most helpful comment
I don't think anything changes.
My recommendation is to always have an
option go_packagecontaining the full import path of the Go package in every.protofile, and to always include thepaths=source_relativegenerator option. The former ensures imports of the package use the right import path, and the latter puts your output files where you (probably) expect them.