-
Bug
-
Resolution: Fixed
-
P2: Important
-
6.8.0
-
All
-
4e8dddcb2 (dev), 3b11e0ec1 (6.9), 4faa8e5d3 (6.8), 00a86d9d2 (dev), 4c82a5762 (6.9), 9f733d53e (6.8)
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.
| For Gerrit Dashboard: QTBUG-130555 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 604557,23 | JSON serialization of google::protobuf::Timestamp well-known type | dev | qt/qtgrpc | Status: MERGED | +2 | +1 |
| 604594,2 | JSON serialization of google::protobuf::Timestamp well-known type | dev | qt/qtgrpc | Status: ABANDONED | 0 | 0 |
| 615099,2 | JSON serialization of google::protobuf::Timestamp well-known type | 6.9 | qt/qtgrpc | Status: MERGED | +2 | 0 |
| 615167,2 | JSON serialization of google::protobuf::Timestamp well-known type | 6.8 | qt/qtgrpc | Status: MERGED | +2 | 0 |
| 616341,11 | Handle special cases of JSON serializing of the Well-known types | dev | qt/qtgrpc | Status: MERGED | +2 | 0 |
| 618041,3 | Handle special cases of JSON serializing of the Well-known types | 6.9 | qt/qtgrpc | Status: MERGED | +2 | 0 |
| 618229,4 | Handle special cases of JSON serializing of the Well-known types | 6.8 | qt/qtgrpc | Status: MERGED | +2 | 0 |