relative .pb.go generation, go_package set to package name #969
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
addresses #962
In the .proto file,
option go_package
is used for pointing to the generated pb package. I'm importing the cloudevents.proto for creating gRPC handlers functions that accept a CloudEvent, but the import breaks becausego_package
points to a local path.I set
go_package
togithub.com/cloudevents/sdk-go/binding/format/protobuf/v2/pb
which Go is able to resolve. However generation was broken until I found this protoc flag in a StackOverflow answer:--go-opts=paths=source_relative
.I also changed the package name to
io.cloudevents.v1
, just like the format here. Package names are supposed to be unique so there aren't collisions when importing multiple protobuf files.