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
Is your feature request related to a problem? Please describe.
I'm always frustrated when I use node as a interface gateway, it call the backend with grpc, and reply to the client with json,
call message.toObject() always get the { seconds: XXX, nanos: XXXX} object with timestamp.
A standard json timestamp should be like "2017-05-04 T00:20:30Z", which is a javascript Date Object turned to be.
Describe the solution you'd like
we should change the protobuf.Timestamp.toObject() function to some like the toDate() function
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I'm always frustrated when I use node as a interface gateway, it call the backend with grpc, and reply to the client with json,
call message.toObject() always get the { seconds: XXX, nanos: XXXX} object with timestamp.
A standard json timestamp should be like "2017-05-04 T00:20:30Z", which is a javascript Date Object turned to be.
Describe the solution you'd like
we should change the protobuf.Timestamp.toObject() function to some like the toDate() function
The text was updated successfully, but these errors were encountered: