Google.Protobuf.Reflection.MessageOptions

public sealed class MessageOptions : IExtendableMessage<MessageOptions>, IMessage<MessageOptions>, IMessage, IEquatable<MessageOptions>, IDeepCloneable<MessageOptions>, IBufferMessage

public const int DeprecatedFieldNumber = 3

Field number for the "deprecated" field.

public const int DeprecatedLegacyJsonFieldConflictsFieldNumber = 11

Field number for the "deprecated_legacy_json_field_conflicts" field.

public const int FeaturesFieldNumber = 12

Field number for the "features" field.

public const int MapEntryFieldNumber = 7

Field number for the "map_entry" field.

public const int MessageSetWireFormatFieldNumber = 1

Field number for the "message_set_wire_format" field.

public const int NoStandardDescriptorAccessorFieldNumber = 2

Field number for the "no_standard_descriptor_accessor" field.

public const int UninterpretedOptionFieldNumber = 999

Field number for the "uninterpreted_option" field.

public static MessageDescriptor Descriptor { get; }

public static MessageParser<MessageOptions> Parser { get; }

public bool Deprecated { get; set; }

Is this message deprecated? Depending on the target platform, this can emit Deprecated annotations for the message, or it will be completely ignored; in the very least, this is a formalization for deprecating messages.

public bool DeprecatedLegacyJsonFieldConflicts { get; set; }

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. This should only be used as a temporary measure against broken builds due to the change in behavior for JSON field name conflicts. TODO This is legacy behavior we plan to remove once downstream teams have had time to migrate.

public FeatureSet Features { get; set; }

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.

public bool HasDeprecated { get; }

Gets whether the "deprecated" field is set

public bool HasDeprecatedLegacyJsonFieldConflicts { get; }

Gets whether the "deprecated_legacy_json_field_conflicts" field is set

public bool HasMapEntry { get; }

Gets whether the "map_entry" field is set

public bool HasMessageSetWireFormat { get; }

Gets whether the "message_set_wire_format" field is set

public bool HasNoStandardDescriptorAccessor { get; }

Gets whether the "no_standard_descriptor_accessor" field is set

public bool MapEntry { get; set; }

Whether the message is an automatically generated map entry type for the maps field. For maps fields: map<KeyType, ValueType> map_field = 1; The parsed descriptor looks like: message MapFieldEntry { option map_entry = true; optional KeyType key = 1; optional ValueType value = 2; } repeated MapFieldEntry map_field = 1; Implementations may choose not to generate the map_entry=true message, but use a native map in the target language to hold the keys and values. The reflection APIs in such implementations still need to work as if the field is a repeated message field. NOTE: Do not set the option in .proto files. Always use the maps syntax instead. The option should only be implicitly set by the proto compiler parser.

public bool MessageSetWireFormat { get; set; }

Set true to use the old proto1 MessageSet wire format for extensions. This is provided for backwards-compatibility with the MessageSet wire format. You should not use this for any other reason: It's less efficient, has fewer features, and is more complicated. The message must be defined exactly as follows: message Foo { option message_set_wire_format = true; extensions 4 to max; } Note that the message cannot have any defined fields; MessageSets only have extensions. All extensions of your type must be singular messages; e.g. they cannot be int32s, enums, or repeated messages. Because this is an option, the above two restrictions are not enforced by the protocol compiler.

public bool NoStandardDescriptorAccessor { get; set; }

Disables the generation of the standard "descriptor()" accessor, which can conflict with a field of the same name. This is meant to make migration from proto1 easier; new code should avoid fields named "descriptor".

public RepeatedField<UninterpretedOption> UninterpretedOption { get; }

The parser stores options it doesn't recognize here. See above.

public MessageOptions()

public MessageOptions(MessageOptions other)

public int CalculateSize()

public void ClearDeprecated()

Clears the value of the "deprecated" field

public void ClearDeprecatedLegacyJsonFieldConflicts()

Clears the value of the "deprecated_legacy_json_field_conflicts" field

public void ClearExtension<TValue>(Extension<MessageOptions, TValue> extension)

public void ClearExtension<TValue>(RepeatedExtension<MessageOptions, TValue> extension)

public void ClearMapEntry()