Joe Tsai f930b1dc76 encoding/protojson: fix parsing of google.protobuf.Timestamp ...

The Timestamp message uses a subset of RFC 3339.
RFC 3339, section 5.6 specifies that the subsecond field can have
any non-zero number of digits.
On the other hand, the protobuf documentation specifies that Timestamp
uses RFC 3339 with a few restrictions. In other words,
protobuf does NOT use RFC 3339, but rather a subset of it.

An upstream change https://go.dev/cl/425037 modifies the time package
to be internally consistent about handling of extra subsecond digits
allowing it to be more in line with RFC 3339.

Make a corresponding change here to ensure we remain compliant
with protobuf's restricted use of RFC 3339.

Change-Id: Ic145c68492fb41a5f7b79b653f3246dd9091d5d8
Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/425554
Reviewed-by: Damien Neil <dneil@google.com>
Reviewed-by: Lasse Folger <lassefolger@google.com>

2022-08-31 09:28:52 +00:00

..

bench_test.go

types: consistently name generated protos

2019-05-16 21:55:40 +00:00

decode_test.go

all: remove shorthand import aliases

2022-05-24 20:05:50 +00:00

decode.go

all: remove shorthand import aliases

2022-05-24 20:05:50 +00:00

doc.go

protogen, encoding/jsonpb, encoding/textpb: rename packages

2019-05-14 20:33:22 +00:00

encode_test.go

all: remove shorthand import aliases

2022-05-24 20:05:50 +00:00

encode.go

all: remove duplicate imports

2022-05-23 17:24:26 +00:00

well_known_types.go

encoding/protojson: fix parsing of google.protobuf.Timestamp

2022-08-31 09:28:52 +00:00