Michael, They map to field names in the options messages defined in descriptor.proto <https://github.com/protocolbuffers/protobuf/blob/master/src/google/protobuf/descriptor.proto#L286> .
Also, if you define custom options (by extending those options messages), you refer to them using qualified name enclosed in parentheses. That proto file above also serves as a sort of AST for proto source files, where FileDescriptorProto is the root of the AST. You can then look at UninterpretedOption for seeing the AST structure for parsing options. ---- *Josh Humphries* [email protected] On Wed, Oct 31, 2018 at 7:30 PM Michael Powell <[email protected]> wrote: > Hello, > > In the Proto2 specification, "field options" are sort of meta-tucked > away. I don't think the specification really names them. Is there a > list of them somewhere in the docs? > > i.e. field = label type fieldName "=" fieldNumber [ "[" fieldOptions "]" ] > ";" > fieldOptions = fieldOption { "," fieldOption } > fieldOption = optionName "=" constant > > Specifically, "optionName" ? If memory serves from examples, things > like "default" ? > > Thanks! > > Best regards, > > Michael Powell > > -- > You received this message because you are subscribed to the Google Groups > "Protocol Buffers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/protobuf. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
