-
Notifications
You must be signed in to change notification settings - Fork 578
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
*: add proto3 optional support #431
Comments
Just in case someone else also stumbled upon this issue: https://stackoverflow.com/a/46821842/4521547 |
This sounds good, but we'll need to add optional support to PGS. Blocked on lyft/protoc-gen-star/pull/85 |
Looks like this can go ahead now. 🎉 |
Checklist updated with the PR bumping to the newly released |
I assume for this, the templates need to be updated for sure, but are there any additional checks that would need to be added? |
Signed-off-by: Sarthak Gupta <signed@sarthak.sh>
Signed-off-by: Sarthak Gupta <signed@sarthak.sh>
This issue is about support for go or for java too? |
I am waiting for this support for Java |
Hi all, |
There's been some progress (see PRs/issues linked above). It looks like #474 made some progress but needs some changes. |
PGS We're currently pending a few things in to close this out. Most notably:
I am planning to work on this over the weekend & see where I land. @akonradi how feasible is it to split support for different languages into different PRs? While I'll try my best, I can't say I am overly confident with templating for some of these languages tbh. |
Splitting support for different languages across multiple PRs SGTM. |
Any update on this? ✌️ |
Signed-off-by: Sarthak Gupta <signed@sarthak.sh>
Is there any update on this? This is preventing us from using this plugin. |
There's a PR open, if you have any java experience and can give a hand that would help immensely :) |
Not enough to be able to contribute 😬 we are only concerned with the |
same here |
* pgs: support proto3 presence & bump go.mod (#431) Signed-off-by: Sarthak Gupta <signed@sarthak.sh> * bump lyft/protoc-gen-start to v0.6.0 Signed-off-by: Mitchell Bundy <mitchell.bundy@unity3d.com> * bump protoc-gen-star to 0.6.0 in bazel dependencies Signed-off-by: Mitchell Bundy <mitchell.bundy@unity3d.com> * add 'optional.proto' file to test harness Signed-off-by: Mitchell Bundy <mitchell.bundy@unity3d.com> * add supported feature optional to go init Signed-off-by: Mitchell Bundy <mitchell.bundy@unity3d.com> * add types/pluginpb to list of deps in BUILD Signed-off-by: Mitchell Bundy <mitchell.bundy@unity3d.com> * bump protobuf in bazel deps to match go.mod version, add deps to BUILD Signed-off-by: Mitchell Bundy <mitchell.bundy@unity3d.com> * bump com_google_protobuf to v3.15.3, matches go-protobuf v1.27 dependency Signed-off-by: Mitchell Bundy <mitchell.bundy@unity3d.com> * update optional test to include optional int64 field within message Signed-off-by: Mitchell Bundy <mitchell.bundy@unity3d.com> * add some test cases to try out Signed-off-by: Mitchell Bundy <mitchell.bundy@unity3d.com> * remove optionalCases from cases Signed-off-by: Mitchell Bundy <mitchell.bundy@unity3d.com> Co-authored-by: Sarthak Gupta <signed@sarthak.sh> Co-authored-by: Ryan Michela <rmichela@salesforce.com>
maybe i am wrong but i think there is already optional support @elliotmjackson |
optionals now no longer make the plugin produce code that doesn't compile. but there are still decisions to be made and validation features to be written. e.g. should things marked not-optional be enforced to be non-null? |
Thank you for your input on adding proto3 optional support to protoc-gen-validate. I'd like to inform you that these capabilities are already available in protovalidate. As we look to the future with protovalidate, we have no intention of expanding support for proto3 optional fields in protoc-gen-validate. I appreciate your understanding. I'll be closing the issue while keeping your suggestion in mind. If you have more questions or need assistance, feel free to reach out. Your engagement is greatly valued! |
I think it would be good to start thinking on how to add support to the proto3 optional keyword.
This feature request could be addressed in two different steps:
optional
support in the libraryWDYT?
The text was updated successfully, but these errors were encountered: