-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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 support for the grpc_api_configuration option in the bazel rule. #632
Conversation
PR grpc-ecosystem#521 added support for grpc service configurations. Add an option to let users specify this config in the bazel rule. Also add a simple doc blob to the rule.
Codecov Report
@@ Coverage Diff @@
## master #632 +/- ##
==========================================
+ Coverage 58.88% 58.94% +0.05%
==========================================
Files 30 30
Lines 2853 2857 +4
==========================================
+ Hits 1680 1684 +4
Misses 1010 1010
Partials 163 163
Continue to review full report at Codecov.
|
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 code looks good to me sans one comment in defs.bzl
.
Could you also add a new target in //examples/proto/examplepb
that runs with grpc_api_configuration
set? Thanks!
protoc-gen-swagger/defs.bzl
Outdated
@@ -36,6 +48,8 @@ def _run_proto_gen_swagger(direct_proto_srcs, transitive_proto_srcs, actions, pr | |||
|
|||
def _proto_gen_swagger_impl(ctx): | |||
proto = ctx.attr.proto.proto | |||
grpc_api_configuration = None |
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.
rm unnecessary line
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.
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.
Not quite done?
But this will fail with:
If I uncomment the 'expamplepb_protoc_gen_swagger' target it works. I would like to investigate this separately (see #638), if that is okay with you. I am not sure about how to resolve this right now. |
Ah, that's totally fair, can you remove that entry from the BUILD file and I'll track doing it in #640 |
You mean removing the example that works right now: Can we not change it when fixing #640? |
I think this is good to go almost. I haven't merged due to https://github.com/grpc-ecosystem/grpc-gateway/pull/632/files#diff-256f5102c31109d1da9e7ebdbde6813cR51 where I asked for a change but I can't see the change. Am I missing something? |
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
…rpc-ecosystem#632) * Add support for the grpc_api_configuration option in the bazel rule. PR grpc-ecosystem#521 added support for grpc service configurations. Add an option to let users specify this config in the bazel rule.
PR #521 added support for grpc service configurations. Add an option to let
users specify this config in the bazel rule.
Also add a simple doc blob to the rule.