-
-
Notifications
You must be signed in to change notification settings - Fork 609
New issue
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
Import GRPC and a simple core.proto file #1651
Conversation
|
|
(You also need to disable the I'm not sure this is the best approach. I think we should probably wait to vendor everything once we actually have a PR that's ready to land. Also I think we should discuss the best way to organize protobuf files out of band, lumping everything into a single giant file is going to lead to having a mess of the same size as the current RPC layer (albiet somewhat easier to understand). Given we already split each service into its own subpackage why not have a single protobuf file for each service? This should reduce confusion, and more importantly the compulsion to copy and paste everything. Since protobuf definitions allow imports we can also bypass repeated definitions of core types by having a protobuf companion to |
I'd also recommend that instead of using |
|
Yeah, that was the plan. core.proto plus service_name.proto, but all files inside rpc/pb.
Er, vendored dependencies don't update by themselves. |
This splits out the godeps changes from #1647, and adds
make grpc
to the Makefile, which will be used to rebuild all protobuf files.