-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Introduce quarkus-grpc-kotlin
extension
#46698
Conversation
/** | ||
* Simple SPI that allows code to add additional options to the gRPC code generation invocation | ||
*/ | ||
public interface AdditionalOutputHandler { |
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.
The signatures of the methods of this maybe overkill for what we want now, but I did it this way just to make sure we don't break anyone if we decide that we need more stuff in the future.
I'm open to just using what we need though if we think this is unlikely to ever change or be used elsewhere
This comment has been minimized.
This comment has been minimized.
f9c1123
to
e96a2e7
Compare
It seems like this doesn't work in practice because the generation and compilation stage happens before Quarkus can add the conditional dependency to the classpath... |
This comment has been minimized.
This comment has been minimized.
🎊 PR Preview 58ff745 has been successfully built and deployed to https://quarkus-pr-main-46698-preview.surge.sh/version/main/guides/
|
This is automatically added by Quarkus during build time if both the `quarkus-grpc` and `quarkus-kotlin` extensions are present. Currently, all the extension does is plug into the gRPC codegen phase. Fixes: quarkusio#46675
Status for workflow
|
Status for workflow
|
This is automatically added by Quarkus during build time if both the
quarkus-grpc
andquarkus-kotlin
extensions are present.Currently, all the extension does is plug into the gRPC codegen phase.