-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Compile google/protobuf/*.proto files into golang structs and add to a new package #50
Comments
@peter-edge Hi. Sorry for this, but I just started doing:
Because works. Let me know if I can do anything to help maintain. I'm not sure of how it might be integrated into this project, exactly. But yeah... I have this problem, too. |
Why are you so awesome? Thanks. ❤️ |
This would be awesome. It would make using protobuf with Go significantly easier |
build protoc version:
error message:
|
😽 |
It would be really nice to have those packages compiled |
This introduces supported Go packages for each well-known type, and a placeholder support package for interacting with them. This commit adds Any, Duration and Empty; more types will follow. Updates #50.
8ea33d2 adds some initial types. I'll add more shortly. |
There's zero diff from the google/protobuf .proto files (except for adding a I put them in separate Go packages since that seemed to make more sense to me, and couldn't think of compelling reasons for them to all be in the same package (their existing package declarations notwithstanding). But I'm happy to hear arguments for them all going together. |
Any arguments, @peter-edge? |
Okay, I'll leave it as I have it now. Neither approach is perfect, and we can consider changing it in the future, but the current state should be fine. |
About date/durations, how about creating some func to get/set timestamps from golang time ? Like Directly in the timestamp pkg, I think it's fine if it's not generated. |
I think you are looking for... Btw, I don't think your comment is related to the original issue. |
I would be happy to do the work and commit it over, but before doing any work on this, wanted to see how open the maintainers were to it. Thoughts?
Also addresses #49
The text was updated successfully, but these errors were encountered: