We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For example in Go it's possible to generate also all the client/server calls.
This avoids the tedious work of matching the request/response types, importing all Protos, etc.
The text was updated successfully, but these errors were encountered:
I'm not sure exactly what you'd anticipate to be generated here. For example, if you take a look at https://github.com/well-typed/grapesy/blob/main/demo-client/Demo/Client/API/Protobuf/IO/RouteGuide.hs , which is the standard Protobuf RouteGuide example, there's barely any boilerplate required at all without generation. What did you have in mind?
Sorry, something went wrong.
I have a grpc with a few thousand rpc calls, so while I can manually add them, it would save time to just have req/resp calls generated.
Given a .proto snippet:
.proto
... service Service { rpc ReqResource(Request) returns (Response) { ...
It would generate:
reqResource :: Client.CanCallRPC m => Request -> m Response reqResource req = Client.nonStreaming (Client.rpc @(Client.Protobuf Service "reqResource") req
And other variants for streaming, etc.
Especially convenient when support for #85 is in.
No branches or pull requests
For example in Go it's possible to generate also all the client/server calls.
This avoids the tedious work of matching the request/response types, importing all Protos, etc.
The text was updated successfully, but these errors were encountered: