I didn't like how pprint.pprint handles protobufs (it does not indent them
properly), so I hacked it a bit:
https://github.com/jayeye/jum/blob/master/src/python/org/tla/proto/pprint.py
Enjoy,
/ji
--
You received this message because you are subscribed to the Google Groups
"Protocol Buffers"
1. During the loading phase, bring the google/protobuf into your WORKSPACE
so you can refer to it as @com_github_google_protobuf later. The bazel
convention is to have fully qualified names, flattening special characters
to underscore.
git_repository(
name = "com_github_google_protobuf",
On Thu, Aug 4, 2016 at 5:47 AM, Philipp Weissenbacher <
philipp.weissenbac...@gmail.com> wrote:
> Hi all,
>
> We are currently implementing a testing library. One goal is to allow the
> client to test sending and receiving ProtoBuf messages.
> For this, we need a generic way to create them,
Hi all,
We are currently implementing a testing library. One goal is to allow the
client to test sending and receiving ProtoBuf messages.
For this, we need a generic way to create them, without requiring the
client to supply the generated proxy classes.
This means MyType.getDefaultInstance()
You need to invoke the grpc plugin. The default protoc tool does not
generate gRPC stubs on it's own. Here's what it looks like:
$ protoc --cpp_out=outdir \
--plugin=protoc-gen-grpc=path/to/the/grpc-cpp-plugin \
--grpc_out=outdir \
path/to/your/helloworld.proto
# Generated by protoc
Hello,
As per the language guide, defining a service in a .proto file will
generate RPC stubs which we can implement (or let gRPC implement).
https://developers.google.com/protocol-buffers/docs/proto3#services
We have a zeroMQ service that we are interested in migrating from JSON-RPC
to gRPC.
