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
In version 0.1.1, disabling feature transport in both tonic and tonic-build results in generated server code that does not compile due to an unconditional dependency on tonic::codegen::HyperBody.
Such coupling is not present in the client code, where it is possible to use the generic client with other Service impls, not necessarily dependent on hyper.
Proposal
The generated Service impl should be generic over the body type, with suitable bounds that are implemented for hyper::Body.
The text was updated successfully, but these errors were encountered:
Feature Request
Crates
tonic-build
Motivation
In version 0.1.1, disabling feature
transport
in both tonic and tonic-build results in generated server code that does not compile due to an unconditional dependency ontonic::codegen::HyperBody
.Such coupling is not present in the client code, where it is possible to use the generic client with other
Service
impls, not necessarily dependent onhyper
.Proposal
The generated
Service
impl should be generic over the body type, with suitable bounds that are implemented forhyper::Body
.The text was updated successfully, but these errors were encountered: