Class DescriptorProtos.MessageOptions.Builder

    • Constructor Detail

      • Builder

        private Builder()
    • Method Detail

      • hasMessageSetWireFormat

        public boolean hasMessageSetWireFormat()
         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.
         
        optional bool message_set_wire_format = 1 [default = false];
        Specified by:
        hasMessageSetWireFormat in interface DescriptorProtos.MessageOptionsOrBuilder
        Returns:
        Whether the messageSetWireFormat field is set.
      • getMessageSetWireFormat

        public boolean getMessageSetWireFormat()
         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.
         
        optional bool message_set_wire_format = 1 [default = false];
        Specified by:
        getMessageSetWireFormat in interface DescriptorProtos.MessageOptionsOrBuilder
        Returns:
        The messageSetWireFormat.
      • setMessageSetWireFormat

        public DescriptorProtos.MessageOptions.Builder setMessageSetWireFormat​(boolean value)
         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.
         
        optional bool message_set_wire_format = 1 [default = false];
        Parameters:
        value - The messageSetWireFormat to set.
        Returns:
        This builder for chaining.
      • clearMessageSetWireFormat

        public DescriptorProtos.MessageOptions.Builder clearMessageSetWireFormat()
         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.
         
        optional bool message_set_wire_format = 1 [default = false];
        Returns:
        This builder for chaining.
      • hasNoStandardDescriptorAccessor

        public boolean hasNoStandardDescriptorAccessor()
         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".
         
        optional bool no_standard_descriptor_accessor = 2 [default = false];
        Specified by:
        hasNoStandardDescriptorAccessor in interface DescriptorProtos.MessageOptionsOrBuilder
        Returns:
        Whether the noStandardDescriptorAccessor field is set.
      • getNoStandardDescriptorAccessor

        public boolean getNoStandardDescriptorAccessor()
         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".
         
        optional bool no_standard_descriptor_accessor = 2 [default = false];
        Specified by:
        getNoStandardDescriptorAccessor in interface DescriptorProtos.MessageOptionsOrBuilder
        Returns:
        The noStandardDescriptorAccessor.
      • setNoStandardDescriptorAccessor

        public DescriptorProtos.MessageOptions.Builder setNoStandardDescriptorAccessor​(boolean value)
         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".
         
        optional bool no_standard_descriptor_accessor = 2 [default = false];
        Parameters:
        value - The noStandardDescriptorAccessor to set.
        Returns:
        This builder for chaining.
      • clearNoStandardDescriptorAccessor

        public DescriptorProtos.MessageOptions.Builder clearNoStandardDescriptorAccessor()
         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".
         
        optional bool no_standard_descriptor_accessor = 2 [default = false];
        Returns:
        This builder for chaining.
      • hasDeprecated

        public boolean hasDeprecated()
         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.
         
        optional bool deprecated = 3 [default = false];
        Specified by:
        hasDeprecated in interface DescriptorProtos.MessageOptionsOrBuilder
        Returns:
        Whether the deprecated field is set.
      • getDeprecated

        public boolean getDeprecated()
         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.
         
        optional bool deprecated = 3 [default = false];
        Specified by:
        getDeprecated in interface DescriptorProtos.MessageOptionsOrBuilder
        Returns:
        The deprecated.
      • setDeprecated

        public DescriptorProtos.MessageOptions.Builder setDeprecated​(boolean value)
         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.
         
        optional bool deprecated = 3 [default = false];
        Parameters:
        value - The deprecated to set.
        Returns:
        This builder for chaining.
      • clearDeprecated

        public DescriptorProtos.MessageOptions.Builder clearDeprecated()
         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.
         
        optional bool deprecated = 3 [default = false];
        Returns:
        This builder for chaining.
      • hasMapEntry

        public boolean hasMapEntry()
         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.
         
        optional bool map_entry = 7;
        Specified by:
        hasMapEntry in interface DescriptorProtos.MessageOptionsOrBuilder
        Returns:
        Whether the mapEntry field is set.
      • getMapEntry

        public boolean getMapEntry()
         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.
         
        optional bool map_entry = 7;
        Specified by:
        getMapEntry in interface DescriptorProtos.MessageOptionsOrBuilder
        Returns:
        The mapEntry.
      • setMapEntry

        public DescriptorProtos.MessageOptions.Builder setMapEntry​(boolean value)
         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.
         
        optional bool map_entry = 7;
        Parameters:
        value - The mapEntry to set.
        Returns:
        This builder for chaining.
      • clearMapEntry

        public DescriptorProtos.MessageOptions.Builder clearMapEntry()
         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.
         
        optional bool map_entry = 7;
        Returns:
        This builder for chaining.
      • hasDeprecatedLegacyJsonFieldConflicts

        @Deprecated
        public boolean hasDeprecatedLegacyJsonFieldConflicts()
        Deprecated.
        google.protobuf.MessageOptions.deprecated_legacy_json_field_conflicts is deprecated. See google/protobuf/descriptor.proto;l=624
         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.
         
        optional bool deprecated_legacy_json_field_conflicts = 11 [deprecated = true];
        Specified by:
        hasDeprecatedLegacyJsonFieldConflicts in interface DescriptorProtos.MessageOptionsOrBuilder
        Returns:
        Whether the deprecatedLegacyJsonFieldConflicts field is set.
      • getDeprecatedLegacyJsonFieldConflicts

        @Deprecated
        public boolean getDeprecatedLegacyJsonFieldConflicts()
        Deprecated.
        google.protobuf.MessageOptions.deprecated_legacy_json_field_conflicts is deprecated. See google/protobuf/descriptor.proto;l=624
         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.
         
        optional bool deprecated_legacy_json_field_conflicts = 11 [deprecated = true];
        Specified by:
        getDeprecatedLegacyJsonFieldConflicts in interface DescriptorProtos.MessageOptionsOrBuilder
        Returns:
        The deprecatedLegacyJsonFieldConflicts.
      • setDeprecatedLegacyJsonFieldConflicts

        @Deprecated
        public DescriptorProtos.MessageOptions.Builder setDeprecatedLegacyJsonFieldConflicts​(boolean value)
        Deprecated.
        google.protobuf.MessageOptions.deprecated_legacy_json_field_conflicts is deprecated. See google/protobuf/descriptor.proto;l=624
         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.
         
        optional bool deprecated_legacy_json_field_conflicts = 11 [deprecated = true];
        Parameters:
        value - The deprecatedLegacyJsonFieldConflicts to set.
        Returns:
        This builder for chaining.
      • clearDeprecatedLegacyJsonFieldConflicts

        @Deprecated
        public DescriptorProtos.MessageOptions.Builder clearDeprecatedLegacyJsonFieldConflicts()
        Deprecated.
        google.protobuf.MessageOptions.deprecated_legacy_json_field_conflicts is deprecated. See google/protobuf/descriptor.proto;l=624
         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.
         
        optional bool deprecated_legacy_json_field_conflicts = 11 [deprecated = true];
        Returns:
        This builder for chaining.
      • hasFeatures

        public boolean hasFeatures()
         Any features defined in the specific edition.
         
        optional .google.protobuf.FeatureSet features = 12;
        Specified by:
        hasFeatures in interface DescriptorProtos.MessageOptionsOrBuilder
        Returns:
        Whether the features field is set.
      • clearUninterpretedOption

        public DescriptorProtos.MessageOptions.Builder clearUninterpretedOption()
         The parser stores options it doesn't recognize here. See above.
         
        repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999;
      • removeUninterpretedOption

        public DescriptorProtos.MessageOptions.Builder removeUninterpretedOption​(int index)
         The parser stores options it doesn't recognize here. See above.
         
        repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999;