Closed johnpryan closed 5 years ago
What versions of everything are you using? Specifically protocol, twirp, bazel, go, os
I believe I'm using the latest versions of everything. I think this has more to do with how I'm using the go_proto_compiler rule.
I suppose my question is if Twirp is a first-class protobuf plugin... or if anyone has an example of a project that is using twirp + bazel.
Thanks!
I'm not very familiar with Bazel so providing support here is difficult, but it appears that protoc-gen-twirp is receiving the "import" parameter which is not supported (and deprecated in the protoc-gen-go generator.
From the documentation here: https://github.com/bazelbuild/rules_go/blob/master/proto/core.rst the one suggestion I might have for you is to try setting import_path_option to "False". I'm not sure if this will cause other problems with your configuration though.
Closing this issue as it doesn't appear to necessarily be a bug in Twirp, and we haven't heard back. Please feel free to add a comment here if you have further questions.
Hi, thank you for making such a great tool.
I am trying to add Bazel support to Twirp here, but I don't quite know how to do it. It's difficult to see how the protoc-gen-twirp binary is being used by protoc (after installing the package using
go get
.)I am currently trying to use protoc-gen-twirp as a go_proto_compiler rule:
But I'm getting an error where the options go_proto_compiler sends to plugins don't match up with what
protoc-gen-twirp
expects:It seems like
protoc-gen-twirp
does not work the same way as gRPC, since it does not use the same Generator type defined ingithub.com/golang/protobuf/protoc-gen-go/generator
?