Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible to support other codec? #457

Open
jeffawx opened this issue Apr 12, 2024 · 1 comment
Open

Possible to support other codec? #457

jeffawx opened this issue Apr 12, 2024 · 1 comment

Comments

@jeffawx
Copy link

jeffawx commented Apr 12, 2024

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?

@dragonsinth
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants