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
I have a request message with google.protobuf.BoolValue name = 1 as a field. When I define a value for this field in Typescript like name: { value: false }, then I see that the request made by the generated code does not include the parameter for this field.
It appears that renderURLSearchParams strips out all primitive types with zero values, but that's not expected for BoolValue, since the whole point is to be able to differentiate between false and nil.
Is there an established way to fix issues like this within this library? I see #25 and cresta#1, but it doesn't include BoolValue or the other wrapper well-known types.
The text was updated successfully, but these errors were encountered:
Same problem occurs with StringValue and the other wrapper types as well. The zero values are removed rather than serialized.
seanami
changed the title
renderURLSearchParams doesn't render BoolValue well-known type correctly
renderURLSearchParams doesn't render BoolValue and other well-known wrapper types correctly
Mar 22, 2023
I have a request message with
google.protobuf.BoolValue name = 1
as a field. When I define a value for this field in Typescript likename: { value: false }
, then I see that the request made by the generated code does not include the parameter for this field.It appears that
renderURLSearchParams
strips out all primitive types with zero values, but that's not expected forBoolValue
, since the whole point is to be able to differentiate between false and nil.Is there an established way to fix issues like this within this library? I see #25 and cresta#1, but it doesn't include
BoolValue
or the other wrapper well-known types.The text was updated successfully, but these errors were encountered: