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
For RPC methods accepting bytes, grpcurl seems to accept a base64-encoded string. Evans differs here, and wants manual bytes literal or unicode literals. These are pretty hard to generate - base64 is easier to copy too.
Similar to #280, what about a call MyRPCMethod --bytes-as-base64, or potentially even changing the default to match grpcurl behaviour?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
For RPC methods accepting bytes, grpcurl seems to accept a base64-encoded string. Evans differs here, and wants manual bytes literal or unicode literals. These are pretty hard to generate - base64 is easier to copy too.
Similar to #280, what about a
call MyRPCMethod --bytes-as-base64
, or potentially even changing the default to matchgrpcurl
behaviour?Beta Was this translation helpful? Give feedback.
All reactions