Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Create @GrpcClass annotation processor hook for generated source files.
See original GitHub issueTo write an annotation processor that further augments the generated source from the grpc protoc plugin is a little difficult.
Currently, I process @Generated annotations and search for value ~= /gRpc/.
As an external example, looking at the new grpc-dagger in 2.11 (google/dagger#647), the additional dagger code generation is triggered off of an annotation applied to the implementing class. It would be nice to have all the code generation based off of the gprc classes. Right now it feels like a two step process. Add the proto, generate the grpc stub, implement the stub, add the processor annotation, compile again for the additional code.
WDYT?
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This was partially addressed in #4609. The RpcService still doesn’t have an annotation, but it could follow in the same vein.
@daicoden What plugin are you using to allow dagger to create the auto generated files upon compilation? I’ve referenced my issue on the Dagger project https://github.com/google/dagger/issues/2157. Your help is greatly appreciated.