You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The prototext package follows the protocol buffer Text Format Language Specification. And that specification does not provide any special handling for well-known types.
Currently, there is no special handling for timestamps. A timestamp field in a message is marshalled as seconds and nanoseconds:
For human consumption I think it would be nicer if timestamps were represented as strings:
Presumably, unmarshalling could support both variants.
The text was updated successfully, but these errors were encountered: