Proto messages doesn't always produce canonical JSONs

The generated code for some types (e.g. Timestamp or enum) contain toJson and toJsonString methods. These seems to work when passing a Protobuf message object to JSON.stringify. But, when passing an object which contain such object as a property, this doesn’t work as intended.

In our case Timestamp is serialized as an object of seconds and nanos and enums will serialize into their numbers.

We solved it by passing a replacer to JSON.stringify like:

body: JSON.stringify(
    body, (_, value) => value?.toJson ? value.toJson() : value
),

According to MDN’s docs JSON.stringify looks for the method toJSON and not toJson or toJsonString. Am I missing something?

[smaye81]

Yep. I am planning to publish a release tomorrow (11/23). Will post here when it’s available.

[doron-cohen]

Already using it. Thanks @smaye81 !