Google.Protobuf.Reflection.EnumOptions
public sealed class EnumOptions : IExtendableMessage<EnumOptions>, IMessage<EnumOptions>, IMessage, IEquatable<EnumOptions>, IDeepCloneable<EnumOptions>, IBufferMessage
Field number for the "allow_alias" field.
Field number for the "deprecated" field.
Field number for the "deprecated_legacy_json_field_conflicts" field.
Field number for the "features" field.
Field number for the "uninterpreted_option" field.
Set this option to true to allow mapping different tag names to the same
value.
Is this enum deprecated?
Depending on the target platform, this can emit Deprecated annotations
for the enum, or it will be completely ignored; in the very least, this
is a formalization for deprecating enums.
Enable the legacy handling of JSON field name conflicts. This lowercases
and strips underscored from the fields before comparison in proto3 only.
The new behavior takes `json_name` into account and applies to proto2 as
well.
TODO Remove this legacy behavior once downstream teams have
had time to migrate.
Any features defined in the specific edition.
WARNING: This field should only be used by protobuf plugins or special
cases like the proto compiler. Other uses are discouraged and
developers should rely on the protoreflect APIs for their client language.
Gets whether the "allow_alias" field is set
Gets whether the "deprecated" field is set
Gets whether the "deprecated_legacy_json_field_conflicts" field is set
The parser stores options it doesn't recognize here. See above.
public EnumOptions()
Clears the value of the "allow_alias" field
Clears the value of the "deprecated" field
Clears the value of the "deprecated_legacy_json_field_conflicts" field
public RepeatedField<TValue> GetOrInitializeExtension<TValue>(RepeatedExtension<EnumOptions, TValue> extension)