protobuf idioms#48
Conversation
|
If the maintainers are open to it, I'd love to provide some more suggestions on the protobuf API as well :) |
|
@peter-edge do you have vim config line for .proto files? |
|
On Friday, December 18, 2015, Alexander Morozov [email protected]
|
|
@peter-edge no, I mean like ts and stuff :) My default config uses tabs for it. And even my spaces is always 4. |
|
Also, I'd prefer each commit to be buildable for later bisects. So makes sense to squash last two commits. |
|
Oh haha. Honestly I don't remember and am away from keyboard right now :) On Friday, December 18, 2015, Alexander Morozov [email protected]
|
|
Will also squash when I get back :) also these PRs can be part of a bigger On Friday, December 18, 2015, Peter Edge [email protected] wrote:
|
|
@peter-edge it's always better to post smaller PR. Don't underestimate maintainers laziness :) |
|
Ha. Well I'll take a straightforward abiet lazy maintainer over a volatile On Friday, December 18, 2015, Alexander Morozov [email protected]
|
|
Changes LGTM |
Signed-off-by: Peter Edge <[email protected]> Update code to reflect api.prot
|
Last two commits were squashed into first commit. As to the formatting - I believe proto standard is 2 spaces and I think that's what I normally see (and it is what I always use), but I can poke around more to verify that. |
There was a problem hiding this comment.
Not wars, but we need some style.
There was a problem hiding this comment.
This covers some of it: https://developers.google.com/protocol-buffers/docs/style. Spaces are not covered.
Should we follow https://github.com/google/protobuf/blob/master/conformance/conformance.proto as closely as possible? Seems like 2 space indents but they don't have any convention on lining up fields.
I don't think I am going to be able to work outside of gofmt anymore. It is just too cozy.
There was a problem hiding this comment.
Yeah, it's superhard without gofmt :/
There was a problem hiding this comment.
I just lazily do vim gg=G but ya it messes up sometimes
On Tuesday, January 5, 2016, Alexander Morozov [email protected]
wrote:
In api/grpc/types/api.proto
https://github.com/docker/containerd/pull/48#discussion_r48894868:}
message CreateContainerRequest {
- string id = 1; // ID of container
- string bundlePath = 2; // path to OCI bundle
- string stdin = 3; // path to the file where stdin will be read (optional)
- string stdout = 4; // path to file where stdout will be written (optional)
- string stderr = 5; // path to file where stderr will be written (optional)
- string console = 6; // path to the console for a container (optional)
- string checkpoint = 7; // checkpoint name if you want to create immediate checkpoint (optional)
- string id = 1; // ID of container
Yeah, it's superhard without gofmt :/
—
Reply to this email directly or view it on GitHub
https://github.com/docker/containerd/pull/48/files#r48894868.
|
Hey, any updates on this? I'm assuming no longer wanted? |
|
ping @LK4D4 heh |
|
@peter-edge I actually posted my LGTM |
|
Ah my bad. I don't want to leave PRs in your world without them being taken On Thu, Jan 21, 2016 at 4:04 PM, Alexander Morozov <[email protected]
|
|
Oh wait, I already linked you to that over in golang/protobuf, lol |
|
The way things are moving right now I think we ware going to have to wait for this until we are out of alpha and the apis have stabilized. Thanks for the PR but I'll close this one now so you don't have to worry about rebases and such as we are making a bunch of changes. Thanks again! |
Hardcode libexec paths and var lib paths (fixes SLES)
This PR does a few things:
api.protoapi.protofor a few protobuf idioms, namely that repeated fields are named as singular, underscore instead of camel case, and a longer package name but with thego_packageoption appliedtypes.IO, types.ProcessInfo. These may or may not be something you like, and also the naming needs work.