-
Notifications
You must be signed in to change notification settings - Fork 229
proto3 support for optional #229
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
Comments
Thanks for bringing this up. Looks like this was quite recently added as a fully supported feature: https://github.com/protocolbuffers/protobuf/releases/tag/v3.15.0 This is kinda of a significant change to proto3 semantics, and will take a bit of thought about how to best adapt the API to support it. It doesn't look like the official proto3 guide has been updated to reflect this yet, but I found this guide which looks highly relevant: https://chromium.googlesource.com/external/github.com/protocolbuffers/protobuf/+/refs/heads/master/docs/implementing_proto3_presence.md Updating the Message metadata model to support this should allow the removal of this hack in the plugin:
|
Is there any progess on this? It's currently very important feature for us, and we're forced to use official python protoc plugin for now. |
Hello, this is also very important for us. Is there any plan/timeline for this feature? What can we do to help speed up the implementation? |
My comment on #35 would have made more sense here - the quick-fix might be to just treat |
Are there any news on this? |
Yes this is nearly ready but there is an issue with the fields recursing infinitely #281 |
@Gobot1234 are tests only failing on the pipeline? I ran |
I'm not entirely sure what's up with it, @kalzoo is the person you should be asking if you'd be willing to do some debugging and provide a fix for the failing tests it will get merged and then beta 4 can be shipped with support for this. |
v.2.0.0b4 has just been released and includes support for this. |
This is gonna be a long shot, but I am still seeing this error. I am on version of v.2.0.0b6, I have libprotoc 3.21.9. It should be working for me, but I still run into this error. been stuck for a few days, so if anyone has any ideas please lmk thanks |
Issue still occurring. Error:
Relevant snippet of
|
Use 2.0.0b6 please |
Thanks, that appears to work |
Proto3 supports the optional keyword. All libraries supporting this keyword needs to indicate this explicitly. Otherwise the complication will fail with
is a proto3 file that contains optional fields, but code generator protoc-gen-python_betterproto hasn't been updated to support optional fields in proto3. Please ask the owner of this code generator to support proto3 optional.
Would it be possible to enable proto3 optional?
See this issue for more detail: vmagamedov/grpclib#125
The text was updated successfully, but these errors were encountered: