diff options
| author |  Feng Xiao <xfxyjwf@gmail.com> | 2017-12-12 14:32:28 -0800 |
|---|---|---|
| committer | Feng Xiao <xfxyjwf@gmail.com> | 2017-12-12 14:32:28 -0800 |
| commit | 8489612dadd3775ffbba029a583b6f00e91d0547 (patch) | |
| tree | d0d96763d773558362a62516029dbef5d65b05c0 | |
| parent | 31c54d1289f2ae44158eff631526762366ba1707 (diff) | |
Update comments for Timestamp JSON format.
Clarify that JSON parser are required to accept both UTC and other
timezone offsets.
Fixes issue 3093
| -rw-r--r-- | src/google/protobuf/timestamp.proto | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/src/google/protobuf/timestamp.proto b/src/google/protobuf/timestamp.proto index 6074b1f7..eafb3fa0 100644 --- a/src/google/protobuf/timestamp.proto +++ b/src/google/protobuf/timestamp.proto @@ -103,7 +103,9 @@ option objc_class_prefix = "GPB"; // {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional // seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), // are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone -// is required, though only UTC (as indicated by "Z") is presently supported. +// is required. A proto3 JSON serializer should always use UTC (as indicated by +// "Z") when printing the Timestamp type and a proto3 JSON parser should be +// able to accept both UTC and other timezones (as indicated by an offset). // // For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past // 01:30 UTC on January 15, 2017. |