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
When a MyMsg is sent to an HTTP client (in my case curl) over grpc-gateway with value set to CASE_A (0), the client seem to receive and empty json object with the field my_value omitted all together.
IE, we receive
{}
instead of
{
"my_value": "CASE_A"
}
In jsonpb, we can set jsonpb.Marshaler.EmitDefaults to true to avoid this behavior. Is that also supported in grpc-gateway?
The text was updated successfully, but these errors were encountered:
Consider the following IDL
When a
MyMsg
is sent to an HTTP client (in my case curl) over grpc-gateway with value set toCASE_A
(0), the client seem to receive and empty json object with the fieldmy_value
omitted all together.IE, we receive
instead of
In
jsonpb
, we can setjsonpb.Marshaler.EmitDefaults
totrue
to avoid this behavior. Is that also supported in grpc-gateway?The text was updated successfully, but these errors were encountered: