Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
6.8.0
Description
I'm disappointed/angry/frustrated/embarrassed that things aren't (or, don't seem to be) the way that they are (already) implemented in Qt protobuf, but the attached python script shows how google.protobuf.Timestamp, when using the canonical JSON serializer/deserializer, actually prints/accepts a date-time string instead of the beautiful/elegant/cant-go-wrong nanos+whole_seconds "true" representation of an instance. ugh.
Attachments
Gerrit Reviews
For Gerrit Dashboard: QTBUG-130555 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
604557,10 | JSON serialization of google::protobuf::Timestamp well-known type | dev | qt/qtgrpc | Status: NEW | 0 | +1 |
604594,2 | JSON serialization of google::protobuf::Timestamp well-known type | dev | qt/qtgrpc | Status: ABANDONED | 0 | 0 |