nerdalize / gg Goto Github PK

Returning an error from the gRPC implementation should be handled more gracefully for default implementations by actually encode as JSON but should be customisable if necessary. Also how would we like to deal with errors from code generation itself, can we provide error codes? Maybe those by grpc

You never want trailing whitespaces to influence your url paths. Trim it before it is used for making a request

Often you would like your code to behave differently whenever the server returns an unexpected status code was returned. The default implementation should take care that the body might not contain encoded content in cases and handle this gracefully.

These are currently stored in private members, this should instead be configurable by the users of the generated code.

For example, running gg $(pwd)/my-proto/*.pb.go causes double absolute paths like "/Users/my-user/go/my-proto/Users/my-user/my-proto" resulting in file not found.

Currently, the protobuf json encoder is used to generate json send as body but that encumbers client libraries with including a dependency that they dont need for a very large part.

Users might want to customize the requests for certain endpoints before it is send to the server, for example to add certain headers. Lifecycle hooks should allow for this.

Not all possible scenarios can be covered with generated codes. To allow for fine-grained customisations to how HTTP requests are parsed into the protobuf message it would be usefull to provide hooks that can be implemented for certain endpoints. Specifically after the input has been parsed and before output is send to the client.

gRPC supports ways of calling rpc endpoints that are not (easily) supported by http 1 endpoints. Make sure this is documented and no (standard) code is generated.

Debugging mall functioning endpoints and requests can be hard when you cant print the actual requests and responses to/from the server. Requesters should define a small and simple logging interface that consumers can implement to see what happens in the generated code. It should be such that the standard lib (accidentally) implements this interface.

Protobuf supports a whole bunch of types, make sure the gorilla/schema form decoder supports such kinds of types.