Consider "message Foo { optional uint32 bar = 1 }". When I decode a
json-string {"bar": -1}, using Pbjson, into the structure Foo, the workflow
used to throw an exception because of the uint32 and "-1". Now, it
effectively sets the field to 2**32-1 and does not throw an exception. I
can imagine something like following happens, somewhere in Protobuf +
Pbjson:
void DoSomething(unsigned int x) {...}
and we call DoSomething(-1).
Is anyone aware of a change in Protobuf that potentially could have cause
this change of behavior?
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/protobuf/d3bd43e9-ebbf-4a2a-979e-7e6e478b0d07n%40googlegroups.com.
