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
But soon realise I can't find tooling to test my application unless I rollout my own.
Question: is it possible for grpcurl to be tweaked to support other payload type other than protobuf? The user interface is pretty much same because we get json input anyway.
Or is this quite a big change won't be in the roadmap?
The text was updated successfully, but these errors were encountered:
That seems pretty out of scope to me. It would be impossible to compile in every possible serializer and deserializer into the client. You could certainly roll your own based on our code base.
Half of the value in grpcurl is in dealing with protos anyway.
If you're using json as a transport natively, you could do we we do and register HTTP handlers that you can just curl
Currently I am looking at code first gRPC with JSON as payload instead of protobuf.
For example: https://grpc.io/blog/grpc-with-json/
But soon realise I can't find tooling to test my application unless I rollout my own.
Question: is it possible for
grpcurl
to be tweaked to support other payload type other than protobuf? The user interface is pretty much same because we get json input anyway.Or is this quite a big change won't be in the roadmap?
The text was updated successfully, but these errors were encountered: