alan you talked about custom error handling not being easy with grpc . If we consider: message Data(define here the actual data that would be in the response for successful call) message Error ( string name=1 ; //could store the attribute that cause the error string message=2 ; //the actual description of the error ) And finally message Response ( Data data=1; repeated Error error=2; ) Wouldn't it fit the purpose and be pretty flexible ? We then check if grpc error code is not nil and check for errors descriptions if any, else consider the default error message matching the error code
"Never have to write another REST Client Library". YA BUDDY NEVER GONNA HAPPEN. By the way I used GRPC. Documentation is really poor so if you guys want people to use it. Improve the documentation!
alan you talked about custom error handling not being easy with grpc . If we consider:
message Data(define here the actual data that would be in the response for successful call)
message Error (
string name=1 ; //could store the attribute that cause the error
string message=2 ; //the actual description of the error
)
And finally
message Response (
Data data=1;
repeated Error error=2;
)
Wouldn't it fit the purpose and be pretty flexible ? We then check if grpc error code is not nil and check for errors descriptions if any, else consider the default error message matching the error code
What's going on with the font
Great talk and great explanation
Great talk. Thanks, Alan!
"Never have to write another REST Client Library". YA BUDDY NEVER GONNA HAPPEN. By the way I used GRPC. Documentation is really poor so if you guys want people to use it. Improve the documentation!
Did you got any kind of improvement can you share me the resources
@@i-am-learning-life i just read past this another 2 years later and i am just curious if the issue has been addressed to OPs liking.
Great talk. Thanks, Alan!