Use proto2, which has the has_* checks per field. (Using get_* you still get the default value, of course.) It's extremely unfortunate that this functionality was removed in proto3, I see that making proto3 unattractive for all but the simplest uses of protos. I know in almost every protobuf use-case I've had, the presence accessors were imperative to proper operation.
On Sat, Mar 26, 2016 at 2:43 PM, Yoav H <joe.daily.j...@gmail.com> wrote: > Hi, > > I wanted ask regarding the decision to populate fields with default values, > even if they do not appear in the encoded message. > If I want to send a "patch" message, where I want to update just the > provided fields, how can I do that with protobuf (without adding IsXXXSet > for every field)? > > Why not add another type, representing a default value? > So the schematics would be, if the field is missing, it is null, and if the > field exists, but with this "missing value" type, it will get the default > value? > > Thanks, > Yoav. > > -- > You received this message because you are subscribed to the Google Groups > "Protocol Buffers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to protobuf+unsubscr...@googlegroups.com. > To post to this group, send email to protobuf@googlegroups.com. > Visit this group at https://groups.google.com/group/protobuf. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to protobuf+unsubscr...@googlegroups.com. To post to this group, send email to protobuf@googlegroups.com. Visit this group at https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
