-
Notifications
You must be signed in to change notification settings - Fork 1
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
Remove auto-generated code from source tree? #2
Comments
👍 |
Oh, second consideration. Having generated code commited makes it Go-getable. So we should consider pros and cons also with this in mind. |
If it's going to be a polyglot project, it's not going to be go-gettable for long |
It should perhaps be go-getable, crate-able (what's the Rustonic term?), etc :) Haha, just realized, just for the sake of it, the Pippi project should use Python just to be pip-installable. |
Hahah yeah, sounds better than pipp-able |
Can we find the issue of the gRPC code generation bug so we can track it here? Or the status of the next library version you mentioned? |
Haha, bra timing. Hittade precis https://github.com/golang/protobuf#packages-and-input-paths |
Håller på att fixa |
Hmm, seems like the fix didn't quite work.
|
We get a |
🤔 |
Fanns en annan option |
Hoppas det här inte är ett issue med Go modules (och att det kräver GOPATH). |
We should be able to use https://github.com/golang/protobuf/blob/1680a479a2cfb3fa22b972af7e36d0a0fde47bf8/proto/proto3_proto/proto3.proto#L35 as a reference, they got it working. |
protoc -I$dir --go_out=plugins=grpc,paths=source_relative:$dir $p |
It works! |
Ref: golang/protobuf#748 |
More autogenerated files left to purge.
This was discovered since #4 had more line additions than deletions. A simple sed replace should not have that effect. Edit: lets keep this issue open until we know that all files in the repo are manually created. |
Found another one!
|
Shall we add a |
Well, either that or actually start writing tests haha |
Hehe, both would result in a green master :p |
True true 😁 |
[1]
I generally agree with this view. However, as also mentioned we have to fix the bug from the golang grpc generator. But, when that bug is fixed I think it would be nice to remove the generated source from the tree. Any opinions?
[1]: https://softwareengineering.stackexchange.com/a/192115
The text was updated successfully, but these errors were encountered: