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
Right now, the only way to support transformation of the well known types between proto and json is jsonpb and unfortunately, some well known types such as Struct and Values are not yet supported for transforming from json to proto. (Also, while I haven't investigated this, others have reported here that jsonpb is ~6x slower.)
It will be useful to have some marshallers and unmarshalers for some of the simpler, more commonly used well known types so that one can use these with encoding.json.
If the proposal sounds good, I can create changelists for a few of these well known types.
The text was updated successfully, but these errors were encountered:
Arguably all generated message types ought to implement json.Marshaler and json.Unmarshaler (calling jsonpb under the hood). But that's a separate issue; I don't think adding a special-case for WKTs is appropriate.
Right now, the only way to support transformation of the well known types between proto and json is jsonpb and unfortunately, some well known types such as Struct and Values are not yet supported for transforming from json to proto. (Also, while I haven't investigated this, others have reported here that jsonpb is ~6x slower.)
It will be useful to have some marshallers and unmarshalers for some of the simpler, more commonly used well known types so that one can use these with encoding.json.
If the proposal sounds good, I can create changelists for a few of these well known types.
The text was updated successfully, but these errors were encountered: