Re: [protobuf] scalar types in service RPCs and partial messages

2019-06-29 Thread Marc Gravell
The "why" is because the marshaller assumes the root is a message; however, you should look at "wrappers.proto" - there are well-known wrappers for single values of most common types, including string. Also, prefer "empty.proto" for empty, not your own. On Sat, 29 Jun 2019 at 13:25, Ananya Bhat

[protobuf] scalar types in service RPCs and partial messages

2019-06-29 Thread Ananya Bhat
Hi, I am new to protobuf. I have question related to specifying partial messages as RPC parameters and using scalar types in RPCs for returning simple strings Why message wrappers are required? Please clarify my doubts to decide better message specification I have definition something like below

[protobuf] Re: Service Expected message type

2019-06-29 Thread Ananya Bhat
Hi, I am new to protobuf. I have question related to similar usecase. Please clarify my doubts to decide better message specification I have definition something like below Option A message Student { message Empty { } //Name of the Student optional string name = 1; // Year of Passing optional

[protobuf] Re: Service Expected message type

2019-06-29 Thread Ananya Bhat
Hello, I have similar question related to using message types with string fields e.g. message Document { On Tuesday, September 25, 2018 at 6:41:46 PM UTC+5:30, omid pourhadi wrote: > > Hi, > > I'm new to protobuf and I'm trying to create a simple CRUD app with grpc > my proto file is : > >