We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
go_proto_link currently copies the .pb.go files to the same directory as the .proto file.
go_proto_link
.pb.go
.proto
However, if the .proto file has a options go_package defined, it does not copy to directory specified in the go_options.
options go_package
go_options
For example, given a file:
proto/mypackage/v1/test.proto
package mypackage.v1; option go_package = "github.com/org/repo/go/mypackage/v1;mypackagev1";
Ideally, it would copy test.pb.go to go/mypackage/v1 instead of proto/mypackage/v1.
test.pb.go
go/mypackage/v1
proto/mypackage/v1
One way that this could be accomplished would be by:
importpath
go_proto_library
The text was updated successfully, but these errors were encountered:
No branches or pull requests
go_proto_link
currently copies the.pb.go
files to the same directory as the.proto
file.However, if the
.proto
file has aoptions go_package
defined, it does not copy to directory specified in thego_options
.For example, given a file:
proto/mypackage/v1/test.proto
Ideally, it would copy
test.pb.go
togo/mypackage/v1
instead ofproto/mypackage/v1
.One way that this could be accomplished would be by:
importpath
attribute in thego_proto_link
rule just likego_proto_library
.importpath
fromgo_proto_library
go_proto_link
rule uses the relevant part ofimportpath
to copy to the correct destination directory, creating the path if needed.The text was updated successfully, but these errors were encountered: