-
Notifications
You must be signed in to change notification settings - Fork 423
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
Add code gen config for the module name #2201
Conversation
Modifications: - Add config to the code generator allowing a different module name to be specified. - Remove unused code Result: The grpc module name can be specified in generated code
The API breakage checker is a false positive, this is a
|
The examples are failing on nightly-main and nightly-next because of grpc/grpc-swift-nio-transport#69 (which is yet to be released). |
Why do we need this exactly? Just for testing? If so, can we not make the new |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just one nit
return self.grpcCore + "." + type | ||
} | ||
|
||
func serverRequest(forType type: String?, streaming: Bool) -> ExistingTypeDescription { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: I think having isStreaming
in all these funcs instead of streaming
makes it more consistent with requestResponse
(and it's also more idiomatic).
func serverRequest(forType type: String?, streaming: Bool) -> ExistingTypeDescription { | |
func serverRequest(forType type: String?, isStreaming: Bool) -> ExistingTypeDescription { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done in 8fa87bf
Modifications:
Result:
The grpc module name can be specified in generated code