-
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
Added comments to base_path to explain behavior #919
Conversation
Add base_path docs to explain behavior
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.
Thanks for this, however, could we start the comment out by saying what this does and give an example of where this might be useful, then add the note about how it doesn't change the generated paths in the http field? Thanks.
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.
Great, thanks for this!
Ah, looks like you still need to regenerate the files with this new comment. There's a one liner in CONTRIBUTING.md that should work. |
Are you still interested in this PR? The CI build failure can be fixed by running two simple docker commands and committing the changes:
|
Codecov Report
@@ Coverage Diff @@
## master #919 +/- ##
=======================================
Coverage 53.22% 53.22%
=======================================
Files 40 40
Lines 4004 4004
=======================================
Hits 2131 2131
Misses 1675 1675
Partials 198 198 Continue to review full report at Codecov.
|
Thanks for your contribution! |
* Add base_path docs to explain behavior * Add to 'base_path' description * Regenerated Go code from protobuf * Revert go.mod to previous version Closes grpc-ecosystem#918
Added comments to base_path to explain how it doesn't modify generated paths and has to be handled manually
Closes #918