-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
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
Remove NamedService
bound for tonic_web::enable
#1115
Comments
Yeah, seems fair to remove, I believe we could just pull the path for logging to check the service. |
WDYM by pulling the path? Removing it altogether? |
slinkydeveloper
added a commit
to slinkydeveloper/tonic
that referenced
this issue
Oct 19, 2022
Signed-off-by: slinkydeveloper <[email protected]>
The path from the http Request type that comes in, it should contain something like |
slinkydeveloper
added a commit
to slinkydeveloper/tonic
that referenced
this issue
Oct 24, 2022
Signed-off-by: slinkydeveloper <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
tonic_web::enable
has a bound onNamedService
used only for logging purposes.Version
Crates
tonic-web
Description
This bound is not really needed, and requires to be implemented in cases such as when users manually implement the underlying service. Does it makes sense to remove it?
The text was updated successfully, but these errors were encountered: