-
Notifications
You must be signed in to change notification settings - Fork 420
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
Should we reduce the amount of generated code? #628
Comments
We could actually do away with service name and just inline it into the generated code. We lose the ability to customise the path but to be honest I don't think we actually need that. We'd also be able to get rid of a protocol as well, since WDYT? |
Sorry, I missed that Not feeling strongly about the service name, either; do you think getting rid of |
Not substantial, but it tidies things up a little (and removes something from the API). Do you think users need programmatic access to the service name? If not we could just add it to the generated documentation for the client. I don't think there's a big difference in inlining vs. not inlining the service name so I'm fine with either! |
🤷♂ I guess we could remove the service name for now — further reduces our API surface for 1.0. Can still add back that later on if needed... |
Currently, we have the following in our generated code:
Should we inline these properties (except for
serviceName
) intoGRPCServiceClient
?@glbrntt, what do you think?
The text was updated successfully, but these errors were encountered: