Making a canonical repo for protos and sharing them with the other projects is the best way. If possible, each sub project (like your client, or server) should generate their own stubs independent of the other. Most build tools have a step for generating code.
On Friday, June 30, 2017 at 5:20:55 AM UTC-7, Selcuk Bozdag wrote: > > Hi, > > I have two projects. One for server and the other one is for the client. I > create the proto file inside the server project and let the code generator > to generate server base class, client stub and request/response message > classes. It goes all well for the server side. > > After having the auto-generated files, I'm copying the stub and message > classes to the client project. > > Am I doing right? What are the best practices to create a smooth > development environment for both server and client side? > For example, I've read that one of the software companies have created a > different repo/project for proto files. They use some scripts to copy > around the projects. > > Thanks, > > -- > Selcuk > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/04ab4f53-aae1-46ea-a5db-6327d042c4ac%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
