Closed longshorej closed 4 years ago
Thanks! Yes, we still have some problems when the generated filenames overlap with other imports in the generated code.
The short-path solution in Akka gRPC would be to remove the imports and refer to the explicit FQCN's. That is fairly ugly, though.
A 'fuller' solution might be to make the code generation more intelligent so it knows when it can use imports and when it must use FQCN's. I think that can fall under #641, but almost calls for switching to another code generation library than twirl...
Thanks for the thoughts! Would you accept an ugly short-path solution PR for now?
Thanks for the thoughts! Would you accept an ugly short-path solution PR for now?
Yes, definitely!
(it's also fine if you just fix 'Segment' and not all imports ;) )
This particular instance (and a number of others) were fixed in #1005, thanks for the ping!
Hi! I think there's a bug in the code generation of akka-grpc if
Segment
is used as the name of a message in the protobuf definitions. I suspect the nameSegment
isn't the only one with an issue.Versions used
1.0.0-M1
Expected Behavior
When I run the following:
I expect it to complete successfully.
Actual Behavior
Instead, it fails to complete compilation. When I change
Segment
toSegmentz
in the protobuf definitions, it successfully compiles.Relevant logs
Reproducible Test Case
https://github.com/longshorej/garbage/tree/master/akka-grpc-codegen-issue