For numeric types, contains the original text representation of the value.
For booleans, "true" or "false".
For strings, contains the default text contents (not escaped in any way).
For bytes, contains the C escaped value. All bytes >= 128 are escaped.
TODO(kenton): Base-64 encode?
JSON name of this field. The value is set by protocol compiler. If the
user has set a "json_name" option on this field, that option's value
will be used. Otherwise, it's deduced from the field's name by converting
it to camelCase.
If true, this is a proto3 "optional". When a proto3 field is optional, it
tracks presence regardless of field type.
When proto3_optional is true, this field must be belong to a oneof to
signal to old proto3 clients that presence is tracked for this field. This
oneof is known as a "synthetic" oneof, and this field must be its sole
member (each proto3 optional field gets its own synthetic oneof). Synthetic
oneofs exist in the descriptor only, and do not generate any API. Synthetic
oneofs must be ordered after all "real" oneofs.
For message fields, proto3_optional doesn't create any semantic change,
since non-repeated message fields always track presence. However it still
indicates the semantic detail of whether the user wrote "optional" or not.
This can be useful for round-tripping the .proto file. For consistency we
give message fields a synthetic oneof also, even though it is not required
to track presence. This is especially important because the parser can't
tell if a field is a message or an enum, so it must always create a
synthetic oneof.
Proto2 optional fields do not set this flag, because they already indicate
optional with LABEL_OPTIONAL.
For message and enum types, this is the name of the type. If the name
starts with a '.', it is fully-qualified. Otherwise, C++-like scoping
rules are used to find the type (i.e. first the nested types within this
message are searched, then within the parent, on up to the root
namespace).
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-21 UTC."],[[["`FieldDescriptorProto` is a class that describes a field within a message in Google Protobuf, implementing several interfaces including `IMessage`, `IEquatable`, `IDeepCloneable`, and `IBufferMessage`."],["This class has constructors for creating a new instance or cloning an existing `FieldDescriptorProto` object and includes numerous fields such as `DefaultValueFieldNumber`, `ExtendeeFieldNumber`, and `JsonNameFieldNumber`, each representing specific aspects of a field's definition."],["Key properties of `FieldDescriptorProto` include `DefaultValue`, `Extendee`, `JsonName`, `Label`, `Name`, `Number`, `OneofIndex`, and `Type`, which store information about the field's values, types, and relationships."],["The class also provides various methods for managing and manipulating `FieldDescriptorProto` objects, including `CalculateSize`, `Clone`, `Equals`, `MergeFrom`, `Clear`, `ToString`, and `WriteTo`, and methods for clearing field values."],["The `FieldDescriptorProto` class can be found in the `Google.Protobuf.Reflection` namespace, and belongs to the `Google.Protobuf.dll` assembly."]]],[]]
