but again, not sure why
extensions are useful for published protos where you want others to be able to add their own fields to the type because they can’t change the original definition
otherwise they behave just like normal fields
so there isn’t much reason to use them for structural reasons
message Change {
optional DocumentType document_type = 1;
extensions 200 to max;
}
extend Change {
optional Foo foo_previous = 200;
optional Foo foo_current = 201;
}
extend Change {
optional Bar bar_previous = 300;
optional Bar bar_current = 301;
}
that’s better
you’re still encoding the submessage either way, just in two steps instead of one
correct
gitter is weird about messages
I recently forked the repo, can someone confirm if the current rspec output is this: http://puu.sh/cRHdP/ce2333bd7a.txt
I am new to protobufs
I want to parse a Counter Strike Demo File and apparently its made using protobufs
and I dont know where to start
The extension of a demofile is
.dem and not .proto which is confusing me a bit
This is what they look like: https://www.dropbox.com/sh/nnzz9nddukhipag/AAAmz357W1WYuUozTZasKBeYa?dl=0
Any help/pointers would be appreciated
without the schema files deserializing and working with protobufs are pretty tedious
There is this: https://github.com/bugdone/demoinfogo-linux
I'm trying to create my proto file from this one : https://github.com/google/play-work/blob/master/emm-notifications/src/main/proto/emm_pubsub.proto
any tips ? specialy for package name ?
Hello, I have a question regarding best practices. I have a proto which need to be able to take a list questions, and all questions are different protos, and not all questions are returned everytime, so I have a field
repeated any questionsSo in my code to figure out which question it is I am looking at, I check a string all the questions have. But it seems to me like there would be a better way to handle that, anybody have some good idea? =)
I am new to protobuf, I would like to ask a question
In my solution, I have a generic parser object which has to contains the rules to deserialize the payload I receive. Until now, I only supported CSV and JSon, so every Parser instance was implementing its own json (or csv) schema. This way I could deserialize many different objects with 1 class.
Now I want to extend the support to Protobuf, and I defined a Parser which contains the protobufOuterClass, so when it receives a serialized payload is able to deserialize it and return me a result which is a standard map I create from the deserialized object
Is it possible to create many different OuterClasses which extends a common interface in order to support with this approac different protobuf with my parser class?
