On Mon, Nov 28, 2016 at 9:59 PM, James Philbin <philb...@gmail.com> wrote:
> Hi,
>
> I'm experimenting with converting some proto2 code that uses extensions to
> use proto3 with the Any type. Things seem generally smooth, but one big
> regression I discovered is that text-serialized versions of protobufs with
> Any types now just contain a serialized binary blob, instead of the actual
> message.
>
> E.g. the text-serialized version of something that used extensions for
> proto2:
> ===
> [base.MyMessage.ext] {
> x: 1
> y: 1
> }
> ===
>
> Becomes more like the following in proto3:
> ===
> {
> type_url: "base.MyMessage"
> value: "\010\n\020\024\030\036"
> }
> ===
>
> This seems to make it very hard to use .DebugString() for debugging and
> proto3 for text configuration files (often edited by hand). Is this
> behavior intended?
>
What version of protobuf are you using? If you have the base.MyMessage
built-in your binary, DebugString() should be able to expand that the same
way as for extensions.
>
> Cheers,
> James
>
> --
> 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.
