You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 16, 2021. It is now read-only.
The descriptor.proto bundled is pretty old, and lacks options used in the built-in proto3 types (cc_enable_arenas, csharp_namespace, go_package and objc_class_prefix). The result is an annoying list of errors found if one uses any of these protos. Any chance of updating this file?
As a side note, I can't figure out how to specify my own descriptor.proto file. It's not clear what the options field is relative to (the default just says google/protobuf/descriptor.proto, where is that google folder located?). Nothing I've done seems to make a difference, whether I put in an absolute path, one relative to my home directory or absolute gibberish. It still figures out that java_package is a valid option, but not that go_package is one.
The text was updated successfully, but these errors were encountered:
I am also having issues with this. I have made sure to add the path to "my own" google/protobuf/descriptor.proto in project settings -> Protocol Buffer -> Import Paths, which does not work. Specifying an absolute path does not help either.
The descriptor.proto bundled is pretty old, and lacks options used in the built-in proto3 types (cc_enable_arenas, csharp_namespace, go_package and objc_class_prefix). The result is an annoying list of errors found if one uses any of these protos. Any chance of updating this file?
As a side note, I can't figure out how to specify my own descriptor.proto file. It's not clear what the options field is relative to (the default just says google/protobuf/descriptor.proto, where is that google folder located?). Nothing I've done seems to make a difference, whether I put in an absolute path, one relative to my home directory or absolute gibberish. It still figures out that java_package is a valid option, but not that go_package is one.
The text was updated successfully, but these errors were encountered: