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
Hello, I'd like to see something like Interceptors on the server side, but more akin to the UnaryInterceptor of gRPC-Web. This is something I have appreciated from other server frameworks. This style of interceptor would "wrap" around the service call, which yields the existing functionality of Interceptors (such as vetoing a request) and more. Such "wrapping" interceptors would be able to manipulate both the incoming request as well as the outgoing response.
There are several interesting use cases for this. One such use case would be instrumenting all service calls in a uniform way.
I think it makes sense to deprecate current interceptor functionality and align client and server interceptor APIs. Feel free to contribute PR with the implementation.
Hello, I'd like to see something like
Interceptor
s on the server side, but more akin to the UnaryInterceptor of gRPC-Web. This is something I have appreciated from other server frameworks. This style of interceptor would "wrap" around the service call, which yields the existing functionality ofInterceptor
s (such as vetoing a request) and more. Such "wrapping" interceptors would be able to manipulate both the incoming request as well as the outgoing response.There are several interesting use cases for this. One such use case would be instrumenting all service calls in a uniform way.
The text was updated successfully, but these errors were encountered: