-
Notifications
You must be signed in to change notification settings - Fork 816
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
Cleanup of grpc go generation code #136
Conversation
I'd previously generated this in two places, and looking at it through Godoc, it seemed like a code smell. Having the generated code in a single place seems like the cleaner option.
@enocom Curious if you see any issues here? |
@markmandel Yeah, definitely don't need two generated files. The C++ generated stuff might even be deleted too. In theory, the proto file is enough, but since we're providing a Go library, we might as well have the generated code for people consuming things within |
Personally, I prefer to keep generated files in the repo - makes clear what is going on (the CRD client is all generated too) - as long as it's header'd appropriately. Kinda like vendoring dependencies 😄 |
Also makes it go-gettable |
Build Succeeded 👏 Build Id: a2980d51-f540-4758-95e6-64c07f487614 The following development artifacts have been built, and will exist for the next 30 days:
|
SGTM. Duplicate unnecessary, for sure. |
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.
LGTM.
I'd previously generated this in two places, and looking at it through Godoc, it seemed like a code smell.
Having the generated code in a single place seems like the cleaner option.