Package com.google.protobuf
Class DescriptorProtos.FieldOptions.Builder
java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder<MessageType,BuilderType>
com.google.protobuf.GeneratedMessageLite.Builder<MessageType,BuilderType>
com.google.protobuf.GeneratedMessageLite.ExtendableBuilder<DescriptorProtos.FieldOptions,DescriptorProtos.FieldOptions.Builder>
com.google.protobuf.DescriptorProtos.FieldOptions.Builder
- All Implemented Interfaces:
DescriptorProtos.FieldOptionsOrBuilder,com.google.protobuf.GeneratedMessageLite.ExtendableMessageOrBuilder<DescriptorProtos.FieldOptions,,DescriptorProtos.FieldOptions.Builder> com.google.protobuf.MessageLite.Builder,com.google.protobuf.MessageLiteOrBuilder,Cloneable
- Enclosing class:
- DescriptorProtos.FieldOptions
public static final class DescriptorProtos.FieldOptions.Builder
extends com.google.protobuf.GeneratedMessageLite.ExtendableBuilder<DescriptorProtos.FieldOptions,DescriptorProtos.FieldOptions.Builder>
implements DescriptorProtos.FieldOptionsOrBuilder
Protobuf type
google.protobuf.FieldOptions-
Field Summary
Fields inherited from class com.google.protobuf.GeneratedMessageLite.Builder
instance -
Method Summary
Modifier and TypeMethodDescriptionaddAllTargets(Iterable<? extends DescriptorProtos.FieldOptions.OptionTargetType> values) repeated .google.protobuf.FieldOptions.OptionTargetType targets = 19 [json_name = "targets"];addAllUninterpretedOption(Iterable<? extends DescriptorProtos.UninterpretedOption> values) The parser stores options it doesn't recognize here.repeated .google.protobuf.FieldOptions.OptionTargetType targets = 19 [json_name = "targets"];addUninterpretedOption(int index, DescriptorProtos.UninterpretedOption value) The parser stores options it doesn't recognize here.addUninterpretedOption(int index, DescriptorProtos.UninterpretedOption.Builder builderForValue) The parser stores options it doesn't recognize here.The parser stores options it doesn't recognize here.addUninterpretedOption(DescriptorProtos.UninterpretedOption.Builder builderForValue) The parser stores options it doesn't recognize here.The ctype option instructs the C++ code generator to use a different representation of the field than it normally would.Indicate that the field value should not be printed out when using debug formats, e.g.Is this field deprecated? Depending on the target platform, this can emit Deprecated annotations for accessors, or it will be completely ignored; in the very least, this is a formalization for deprecating fields.The jstype option determines the JavaScript type used for values of the field.Should this field be parsed lazily? Lazy applies only to message-type fields.The packed option can be enabled for repeated primitive fields to enable a more efficient representation on the wire.optional .google.protobuf.FieldOptions.OptionRetention retention = 17 [json_name = "retention"];Deprecated.google.protobuf.FieldOptions.target is deprecated.repeated .google.protobuf.FieldOptions.OptionTargetType targets = 19 [json_name = "targets"];The parser stores options it doesn't recognize here.unverified_lazy does no correctness checks on the byte stream.For Google-internal migration only.getCtype()The ctype option instructs the C++ code generator to use a different representation of the field than it normally would.booleanIndicate that the field value should not be printed out when using debug formats, e.g.booleanIs this field deprecated? Depending on the target platform, this can emit Deprecated annotations for accessors, or it will be completely ignored; in the very least, this is a formalization for deprecating fields.The jstype option determines the JavaScript type used for values of the field.booleangetLazy()Should this field be parsed lazily? Lazy applies only to message-type fields.booleanThe packed option can be enabled for repeated primitive fields to enable a more efficient representation on the wire.optional .google.protobuf.FieldOptions.OptionRetention retention = 17 [json_name = "retention"];Deprecated.google.protobuf.FieldOptions.target is deprecated.getTargets(int index) repeated .google.protobuf.FieldOptions.OptionTargetType targets = 19 [json_name = "targets"];intrepeated .google.protobuf.FieldOptions.OptionTargetType targets = 19 [json_name = "targets"];repeated .google.protobuf.FieldOptions.OptionTargetType targets = 19 [json_name = "targets"];getUninterpretedOption(int index) The parser stores options it doesn't recognize here.intThe parser stores options it doesn't recognize here.The parser stores options it doesn't recognize here.booleanunverified_lazy does no correctness checks on the byte stream.booleangetWeak()For Google-internal migration only.booleanhasCtype()The ctype option instructs the C++ code generator to use a different representation of the field than it normally would.booleanIndicate that the field value should not be printed out when using debug formats, e.g.booleanIs this field deprecated? Depending on the target platform, this can emit Deprecated annotations for accessors, or it will be completely ignored; in the very least, this is a formalization for deprecating fields.booleanThe jstype option determines the JavaScript type used for values of the field.booleanhasLazy()Should this field be parsed lazily? Lazy applies only to message-type fields.booleanThe packed option can be enabled for repeated primitive fields to enable a more efficient representation on the wire.booleanoptional .google.protobuf.FieldOptions.OptionRetention retention = 17 [json_name = "retention"];booleanDeprecated.google.protobuf.FieldOptions.target is deprecated.booleanunverified_lazy does no correctness checks on the byte stream.booleanhasWeak()For Google-internal migration only.removeUninterpretedOption(int index) The parser stores options it doesn't recognize here.The ctype option instructs the C++ code generator to use a different representation of the field than it normally would.setDebugRedact(boolean value) Indicate that the field value should not be printed out when using debug formats, e.g.setDeprecated(boolean value) Is this field deprecated? Depending on the target platform, this can emit Deprecated annotations for accessors, or it will be completely ignored; in the very least, this is a formalization for deprecating fields.The jstype option determines the JavaScript type used for values of the field.setLazy(boolean value) Should this field be parsed lazily? Lazy applies only to message-type fields.setPacked(boolean value) The packed option can be enabled for repeated primitive fields to enable a more efficient representation on the wire.optional .google.protobuf.FieldOptions.OptionRetention retention = 17 [json_name = "retention"];Deprecated.google.protobuf.FieldOptions.target is deprecated.setTargets(int index, DescriptorProtos.FieldOptions.OptionTargetType value) repeated .google.protobuf.FieldOptions.OptionTargetType targets = 19 [json_name = "targets"];setUninterpretedOption(int index, DescriptorProtos.UninterpretedOption value) The parser stores options it doesn't recognize here.setUninterpretedOption(int index, DescriptorProtos.UninterpretedOption.Builder builderForValue) The parser stores options it doesn't recognize here.setUnverifiedLazy(boolean value) unverified_lazy does no correctness checks on the byte stream.setWeak(boolean value) For Google-internal migration only.Methods inherited from class com.google.protobuf.GeneratedMessageLite.ExtendableBuilder
addExtension, buildPartial, clearExtension, copyOnWriteInternal, getExtension, getExtension, getExtensionCount, hasExtension, setExtension, setExtensionMethods inherited from class com.google.protobuf.GeneratedMessageLite.Builder
build, clear, clone, copyOnWrite, getDefaultInstanceForType, internalMergeFrom, isInitialized, mergeFrom, mergeFrom, mergeFrom, mergeFromMethods inherited from class com.google.protobuf.AbstractMessageLite.Builder
addAll, addAll, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageExceptionMethods inherited from class java.lang.Object
equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface com.google.protobuf.GeneratedMessageLite.ExtendableMessageOrBuilder
getExtension, getExtension, getExtensionCount, hasExtensionMethods inherited from interface com.google.protobuf.MessageLiteOrBuilder
getDefaultInstanceForType, isInitialized
-
Method Details
-
hasCtype
public boolean hasCtype()The ctype option instructs the C++ code generator to use a different representation of the field than it normally would. See the specific options below. This option is only implemented to support use of [ctype=CORD] and [ctype=STRING] (the default) on non-repeated fields of type "bytes" in the open source release -- sorry, we'll try to include other types in a future version!
optional .google.protobuf.FieldOptions.CType ctype = 1 [default = STRING, json_name = "ctype"];- Specified by:
hasCtypein interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- Whether the ctype field is set.
-
getCtype
The ctype option instructs the C++ code generator to use a different representation of the field than it normally would. See the specific options below. This option is only implemented to support use of [ctype=CORD] and [ctype=STRING] (the default) on non-repeated fields of type "bytes" in the open source release -- sorry, we'll try to include other types in a future version!
optional .google.protobuf.FieldOptions.CType ctype = 1 [default = STRING, json_name = "ctype"];- Specified by:
getCtypein interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- The ctype.
-
setCtype
The ctype option instructs the C++ code generator to use a different representation of the field than it normally would. See the specific options below. This option is only implemented to support use of [ctype=CORD] and [ctype=STRING] (the default) on non-repeated fields of type "bytes" in the open source release -- sorry, we'll try to include other types in a future version!
optional .google.protobuf.FieldOptions.CType ctype = 1 [default = STRING, json_name = "ctype"];- Parameters:
value- The enum numeric value on the wire for ctype to set.- Returns:
- This builder for chaining.
-
clearCtype
The ctype option instructs the C++ code generator to use a different representation of the field than it normally would. See the specific options below. This option is only implemented to support use of [ctype=CORD] and [ctype=STRING] (the default) on non-repeated fields of type "bytes" in the open source release -- sorry, we'll try to include other types in a future version!
optional .google.protobuf.FieldOptions.CType ctype = 1 [default = STRING, json_name = "ctype"];- Returns:
- This builder for chaining.
-
hasPacked
public boolean hasPacked()The packed option can be enabled for repeated primitive fields to enable a more efficient representation on the wire. Rather than repeatedly writing the tag and type for each element, the entire array is encoded as a single length-delimited blob. In proto3, only explicit setting it to false will avoid using packed encoding.
optional bool packed = 2 [json_name = "packed"];- Specified by:
hasPackedin interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- Whether the packed field is set.
-
getPacked
public boolean getPacked()The packed option can be enabled for repeated primitive fields to enable a more efficient representation on the wire. Rather than repeatedly writing the tag and type for each element, the entire array is encoded as a single length-delimited blob. In proto3, only explicit setting it to false will avoid using packed encoding.
optional bool packed = 2 [json_name = "packed"];- Specified by:
getPackedin interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- The packed.
-
setPacked
The packed option can be enabled for repeated primitive fields to enable a more efficient representation on the wire. Rather than repeatedly writing the tag and type for each element, the entire array is encoded as a single length-delimited blob. In proto3, only explicit setting it to false will avoid using packed encoding.
optional bool packed = 2 [json_name = "packed"];- Parameters:
value- The packed to set.- Returns:
- This builder for chaining.
-
clearPacked
The packed option can be enabled for repeated primitive fields to enable a more efficient representation on the wire. Rather than repeatedly writing the tag and type for each element, the entire array is encoded as a single length-delimited blob. In proto3, only explicit setting it to false will avoid using packed encoding.
optional bool packed = 2 [json_name = "packed"];- Returns:
- This builder for chaining.
-
hasJstype
public boolean hasJstype()The jstype option determines the JavaScript type used for values of the field. The option is permitted only for 64 bit integral and fixed types (int64, uint64, sint64, fixed64, sfixed64). A field with jstype JS_STRING is represented as JavaScript string, which avoids loss of precision that can happen when a large value is converted to a floating point JavaScript. Specifying JS_NUMBER for the jstype causes the generated JavaScript code to use the JavaScript "number" type. The behavior of the default option JS_NORMAL is implementation dependent. This option is an enum to permit additional types to be added, e.g. goog.math.Integer.
optional .google.protobuf.FieldOptions.JSType jstype = 6 [default = JS_NORMAL, json_name = "jstype"];- Specified by:
hasJstypein interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- Whether the jstype field is set.
-
getJstype
The jstype option determines the JavaScript type used for values of the field. The option is permitted only for 64 bit integral and fixed types (int64, uint64, sint64, fixed64, sfixed64). A field with jstype JS_STRING is represented as JavaScript string, which avoids loss of precision that can happen when a large value is converted to a floating point JavaScript. Specifying JS_NUMBER for the jstype causes the generated JavaScript code to use the JavaScript "number" type. The behavior of the default option JS_NORMAL is implementation dependent. This option is an enum to permit additional types to be added, e.g. goog.math.Integer.
optional .google.protobuf.FieldOptions.JSType jstype = 6 [default = JS_NORMAL, json_name = "jstype"];- Specified by:
getJstypein interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- The jstype.
-
setJstype
The jstype option determines the JavaScript type used for values of the field. The option is permitted only for 64 bit integral and fixed types (int64, uint64, sint64, fixed64, sfixed64). A field with jstype JS_STRING is represented as JavaScript string, which avoids loss of precision that can happen when a large value is converted to a floating point JavaScript. Specifying JS_NUMBER for the jstype causes the generated JavaScript code to use the JavaScript "number" type. The behavior of the default option JS_NORMAL is implementation dependent. This option is an enum to permit additional types to be added, e.g. goog.math.Integer.
optional .google.protobuf.FieldOptions.JSType jstype = 6 [default = JS_NORMAL, json_name = "jstype"];- Parameters:
value- The enum numeric value on the wire for jstype to set.- Returns:
- This builder for chaining.
-
clearJstype
The jstype option determines the JavaScript type used for values of the field. The option is permitted only for 64 bit integral and fixed types (int64, uint64, sint64, fixed64, sfixed64). A field with jstype JS_STRING is represented as JavaScript string, which avoids loss of precision that can happen when a large value is converted to a floating point JavaScript. Specifying JS_NUMBER for the jstype causes the generated JavaScript code to use the JavaScript "number" type. The behavior of the default option JS_NORMAL is implementation dependent. This option is an enum to permit additional types to be added, e.g. goog.math.Integer.
optional .google.protobuf.FieldOptions.JSType jstype = 6 [default = JS_NORMAL, json_name = "jstype"];- Returns:
- This builder for chaining.
-
hasLazy
public boolean hasLazy()Should this field be parsed lazily? Lazy applies only to message-type fields. It means that when the outer message is initially parsed, the inner message's contents will not be parsed but instead stored in encoded form. The inner message will actually be parsed when it is first accessed. This is only a hint. Implementations are free to choose whether to use eager or lazy parsing regardless of the value of this option. However, setting this option true suggests that the protocol author believes that using lazy parsing on this field is worth the additional bookkeeping overhead typically needed to implement it. This option does not affect the public interface of any generated code; all method signatures remain the same. Furthermore, thread-safety of the interface is not affected by this option; const methods remain safe to call from multiple threads concurrently, while non-const methods continue to require exclusive access. Note that implementations may choose not to check required fields within a lazy sub-message. That is, calling IsInitialized() on the outer message may return true even if the inner message has missing required fields. This is necessary because otherwise the inner message would have to be parsed in order to perform the check, defeating the purpose of lazy parsing. An implementation which chooses not to check required fields must be consistent about it. That is, for any particular sub-message, the implementation must either *always* check its required fields, or *never* check its required fields, regardless of whether or not the message has been parsed. As of May 2022, lazy verifies the contents of the byte stream during parsing. An invalid byte stream will cause the overall parsing to fail.
optional bool lazy = 5 [default = false, json_name = "lazy"];- Specified by:
hasLazyin interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- Whether the lazy field is set.
-
getLazy
public boolean getLazy()Should this field be parsed lazily? Lazy applies only to message-type fields. It means that when the outer message is initially parsed, the inner message's contents will not be parsed but instead stored in encoded form. The inner message will actually be parsed when it is first accessed. This is only a hint. Implementations are free to choose whether to use eager or lazy parsing regardless of the value of this option. However, setting this option true suggests that the protocol author believes that using lazy parsing on this field is worth the additional bookkeeping overhead typically needed to implement it. This option does not affect the public interface of any generated code; all method signatures remain the same. Furthermore, thread-safety of the interface is not affected by this option; const methods remain safe to call from multiple threads concurrently, while non-const methods continue to require exclusive access. Note that implementations may choose not to check required fields within a lazy sub-message. That is, calling IsInitialized() on the outer message may return true even if the inner message has missing required fields. This is necessary because otherwise the inner message would have to be parsed in order to perform the check, defeating the purpose of lazy parsing. An implementation which chooses not to check required fields must be consistent about it. That is, for any particular sub-message, the implementation must either *always* check its required fields, or *never* check its required fields, regardless of whether or not the message has been parsed. As of May 2022, lazy verifies the contents of the byte stream during parsing. An invalid byte stream will cause the overall parsing to fail.
optional bool lazy = 5 [default = false, json_name = "lazy"];- Specified by:
getLazyin interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- The lazy.
-
setLazy
Should this field be parsed lazily? Lazy applies only to message-type fields. It means that when the outer message is initially parsed, the inner message's contents will not be parsed but instead stored in encoded form. The inner message will actually be parsed when it is first accessed. This is only a hint. Implementations are free to choose whether to use eager or lazy parsing regardless of the value of this option. However, setting this option true suggests that the protocol author believes that using lazy parsing on this field is worth the additional bookkeeping overhead typically needed to implement it. This option does not affect the public interface of any generated code; all method signatures remain the same. Furthermore, thread-safety of the interface is not affected by this option; const methods remain safe to call from multiple threads concurrently, while non-const methods continue to require exclusive access. Note that implementations may choose not to check required fields within a lazy sub-message. That is, calling IsInitialized() on the outer message may return true even if the inner message has missing required fields. This is necessary because otherwise the inner message would have to be parsed in order to perform the check, defeating the purpose of lazy parsing. An implementation which chooses not to check required fields must be consistent about it. That is, for any particular sub-message, the implementation must either *always* check its required fields, or *never* check its required fields, regardless of whether or not the message has been parsed. As of May 2022, lazy verifies the contents of the byte stream during parsing. An invalid byte stream will cause the overall parsing to fail.
optional bool lazy = 5 [default = false, json_name = "lazy"];- Parameters:
value- The lazy to set.- Returns:
- This builder for chaining.
-
clearLazy
Should this field be parsed lazily? Lazy applies only to message-type fields. It means that when the outer message is initially parsed, the inner message's contents will not be parsed but instead stored in encoded form. The inner message will actually be parsed when it is first accessed. This is only a hint. Implementations are free to choose whether to use eager or lazy parsing regardless of the value of this option. However, setting this option true suggests that the protocol author believes that using lazy parsing on this field is worth the additional bookkeeping overhead typically needed to implement it. This option does not affect the public interface of any generated code; all method signatures remain the same. Furthermore, thread-safety of the interface is not affected by this option; const methods remain safe to call from multiple threads concurrently, while non-const methods continue to require exclusive access. Note that implementations may choose not to check required fields within a lazy sub-message. That is, calling IsInitialized() on the outer message may return true even if the inner message has missing required fields. This is necessary because otherwise the inner message would have to be parsed in order to perform the check, defeating the purpose of lazy parsing. An implementation which chooses not to check required fields must be consistent about it. That is, for any particular sub-message, the implementation must either *always* check its required fields, or *never* check its required fields, regardless of whether or not the message has been parsed. As of May 2022, lazy verifies the contents of the byte stream during parsing. An invalid byte stream will cause the overall parsing to fail.
optional bool lazy = 5 [default = false, json_name = "lazy"];- Returns:
- This builder for chaining.
-
hasUnverifiedLazy
public boolean hasUnverifiedLazy()unverified_lazy does no correctness checks on the byte stream. This should only be used where lazy with verification is prohibitive for performance reasons.
optional bool unverified_lazy = 15 [default = false, json_name = "unverifiedLazy"];- Specified by:
hasUnverifiedLazyin interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- Whether the unverifiedLazy field is set.
-
getUnverifiedLazy
public boolean getUnverifiedLazy()unverified_lazy does no correctness checks on the byte stream. This should only be used where lazy with verification is prohibitive for performance reasons.
optional bool unverified_lazy = 15 [default = false, json_name = "unverifiedLazy"];- Specified by:
getUnverifiedLazyin interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- The unverifiedLazy.
-
setUnverifiedLazy
unverified_lazy does no correctness checks on the byte stream. This should only be used where lazy with verification is prohibitive for performance reasons.
optional bool unverified_lazy = 15 [default = false, json_name = "unverifiedLazy"];- Parameters:
value- The unverifiedLazy to set.- Returns:
- This builder for chaining.
-
clearUnverifiedLazy
unverified_lazy does no correctness checks on the byte stream. This should only be used where lazy with verification is prohibitive for performance reasons.
optional bool unverified_lazy = 15 [default = false, json_name = "unverifiedLazy"];- Returns:
- This builder for chaining.
-
hasDeprecated
public boolean hasDeprecated()Is this field deprecated? Depending on the target platform, this can emit Deprecated annotations for accessors, or it will be completely ignored; in the very least, this is a formalization for deprecating fields.
optional bool deprecated = 3 [default = false, json_name = "deprecated"];- Specified by:
hasDeprecatedin interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- Whether the deprecated field is set.
-
getDeprecated
public boolean getDeprecated()Is this field deprecated? Depending on the target platform, this can emit Deprecated annotations for accessors, or it will be completely ignored; in the very least, this is a formalization for deprecating fields.
optional bool deprecated = 3 [default = false, json_name = "deprecated"];- Specified by:
getDeprecatedin interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- The deprecated.
-
setDeprecated
Is this field deprecated? Depending on the target platform, this can emit Deprecated annotations for accessors, or it will be completely ignored; in the very least, this is a formalization for deprecating fields.
optional bool deprecated = 3 [default = false, json_name = "deprecated"];- Parameters:
value- The deprecated to set.- Returns:
- This builder for chaining.
-
clearDeprecated
Is this field deprecated? Depending on the target platform, this can emit Deprecated annotations for accessors, or it will be completely ignored; in the very least, this is a formalization for deprecating fields.
optional bool deprecated = 3 [default = false, json_name = "deprecated"];- Returns:
- This builder for chaining.
-
hasWeak
public boolean hasWeak()For Google-internal migration only. Do not use.
optional bool weak = 10 [default = false, json_name = "weak"];- Specified by:
hasWeakin interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- Whether the weak field is set.
-
getWeak
public boolean getWeak()For Google-internal migration only. Do not use.
optional bool weak = 10 [default = false, json_name = "weak"];- Specified by:
getWeakin interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- The weak.
-
setWeak
For Google-internal migration only. Do not use.
optional bool weak = 10 [default = false, json_name = "weak"];- Parameters:
value- The weak to set.- Returns:
- This builder for chaining.
-
clearWeak
For Google-internal migration only. Do not use.
optional bool weak = 10 [default = false, json_name = "weak"];- Returns:
- This builder for chaining.
-
hasDebugRedact
public boolean hasDebugRedact()Indicate that the field value should not be printed out when using debug formats, e.g. when the field contains sensitive credentials.
optional bool debug_redact = 16 [default = false, json_name = "debugRedact"];- Specified by:
hasDebugRedactin interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- Whether the debugRedact field is set.
-
getDebugRedact
public boolean getDebugRedact()Indicate that the field value should not be printed out when using debug formats, e.g. when the field contains sensitive credentials.
optional bool debug_redact = 16 [default = false, json_name = "debugRedact"];- Specified by:
getDebugRedactin interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- The debugRedact.
-
setDebugRedact
Indicate that the field value should not be printed out when using debug formats, e.g. when the field contains sensitive credentials.
optional bool debug_redact = 16 [default = false, json_name = "debugRedact"];- Parameters:
value- The debugRedact to set.- Returns:
- This builder for chaining.
-
clearDebugRedact
Indicate that the field value should not be printed out when using debug formats, e.g. when the field contains sensitive credentials.
optional bool debug_redact = 16 [default = false, json_name = "debugRedact"];- Returns:
- This builder for chaining.
-
hasRetention
public boolean hasRetention()optional .google.protobuf.FieldOptions.OptionRetention retention = 17 [json_name = "retention"];- Specified by:
hasRetentionin interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- Whether the retention field is set.
-
getRetention
optional .google.protobuf.FieldOptions.OptionRetention retention = 17 [json_name = "retention"];- Specified by:
getRetentionin interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- The retention.
-
setRetention
public DescriptorProtos.FieldOptions.Builder setRetention(DescriptorProtos.FieldOptions.OptionRetention value) optional .google.protobuf.FieldOptions.OptionRetention retention = 17 [json_name = "retention"];- Parameters:
value- The enum numeric value on the wire for retention to set.- Returns:
- This builder for chaining.
-
clearRetention
optional .google.protobuf.FieldOptions.OptionRetention retention = 17 [json_name = "retention"];- Returns:
- This builder for chaining.
-
hasTarget
Deprecated.google.protobuf.FieldOptions.target is deprecated. See google/protobuf/descriptor.proto;l=713optional .google.protobuf.FieldOptions.OptionTargetType target = 18 [json_name = "target", deprecated = true];- Specified by:
hasTargetin interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- Whether the target field is set.
-
getTarget
Deprecated.google.protobuf.FieldOptions.target is deprecated. See google/protobuf/descriptor.proto;l=713optional .google.protobuf.FieldOptions.OptionTargetType target = 18 [json_name = "target", deprecated = true];- Specified by:
getTargetin interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- The target.
-
setTarget
@Deprecated public DescriptorProtos.FieldOptions.Builder setTarget(DescriptorProtos.FieldOptions.OptionTargetType value) Deprecated.google.protobuf.FieldOptions.target is deprecated. See google/protobuf/descriptor.proto;l=713optional .google.protobuf.FieldOptions.OptionTargetType target = 18 [json_name = "target", deprecated = true];- Parameters:
value- The enum numeric value on the wire for target to set.- Returns:
- This builder for chaining.
-
clearTarget
Deprecated.google.protobuf.FieldOptions.target is deprecated. See google/protobuf/descriptor.proto;l=713optional .google.protobuf.FieldOptions.OptionTargetType target = 18 [json_name = "target", deprecated = true];- Returns:
- This builder for chaining.
-
getTargetsList
repeated .google.protobuf.FieldOptions.OptionTargetType targets = 19 [json_name = "targets"];- Specified by:
getTargetsListin interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- A list containing the targets.
-
getTargetsCount
public int getTargetsCount()repeated .google.protobuf.FieldOptions.OptionTargetType targets = 19 [json_name = "targets"];- Specified by:
getTargetsCountin interfaceDescriptorProtos.FieldOptionsOrBuilder- Returns:
- The count of targets.
-
getTargets
repeated .google.protobuf.FieldOptions.OptionTargetType targets = 19 [json_name = "targets"];- Specified by:
getTargetsin interfaceDescriptorProtos.FieldOptionsOrBuilder- Parameters:
index- The index of the element to return.- Returns:
- The targets at the given index.
-
setTargets
public DescriptorProtos.FieldOptions.Builder setTargets(int index, DescriptorProtos.FieldOptions.OptionTargetType value) repeated .google.protobuf.FieldOptions.OptionTargetType targets = 19 [json_name = "targets"];- Parameters:
index- The index to set the value at.value- The targets to set.- Returns:
- This builder for chaining.
-
addTargets
public DescriptorProtos.FieldOptions.Builder addTargets(DescriptorProtos.FieldOptions.OptionTargetType value) repeated .google.protobuf.FieldOptions.OptionTargetType targets = 19 [json_name = "targets"];- Parameters:
value- The targets to add.- Returns:
- This builder for chaining.
-
addAllTargets
public DescriptorProtos.FieldOptions.Builder addAllTargets(Iterable<? extends DescriptorProtos.FieldOptions.OptionTargetType> values) repeated .google.protobuf.FieldOptions.OptionTargetType targets = 19 [json_name = "targets"];- Parameters:
values- The targets to add.- Returns:
- This builder for chaining.
-
clearTargets
repeated .google.protobuf.FieldOptions.OptionTargetType targets = 19 [json_name = "targets"];- Returns:
- This builder for chaining.
-
getUninterpretedOptionList
The parser stores options it doesn't recognize here. See above.
repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999 [json_name = "uninterpretedOption"];- Specified by:
getUninterpretedOptionListin interfaceDescriptorProtos.FieldOptionsOrBuilder
-
getUninterpretedOptionCount
public int getUninterpretedOptionCount()The parser stores options it doesn't recognize here. See above.
repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999 [json_name = "uninterpretedOption"];- Specified by:
getUninterpretedOptionCountin interfaceDescriptorProtos.FieldOptionsOrBuilder
-
getUninterpretedOption
The parser stores options it doesn't recognize here. See above.
repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999 [json_name = "uninterpretedOption"];- Specified by:
getUninterpretedOptionin interfaceDescriptorProtos.FieldOptionsOrBuilder
-
setUninterpretedOption
public DescriptorProtos.FieldOptions.Builder setUninterpretedOption(int index, DescriptorProtos.UninterpretedOption value) The parser stores options it doesn't recognize here. See above.
repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999 [json_name = "uninterpretedOption"]; -
setUninterpretedOption
public DescriptorProtos.FieldOptions.Builder setUninterpretedOption(int index, DescriptorProtos.UninterpretedOption.Builder builderForValue) The parser stores options it doesn't recognize here. See above.
repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999 [json_name = "uninterpretedOption"]; -
addUninterpretedOption
public DescriptorProtos.FieldOptions.Builder addUninterpretedOption(DescriptorProtos.UninterpretedOption value) The parser stores options it doesn't recognize here. See above.
repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999 [json_name = "uninterpretedOption"]; -
addUninterpretedOption
public DescriptorProtos.FieldOptions.Builder addUninterpretedOption(int index, DescriptorProtos.UninterpretedOption value) The parser stores options it doesn't recognize here. See above.
repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999 [json_name = "uninterpretedOption"]; -
addUninterpretedOption
public DescriptorProtos.FieldOptions.Builder addUninterpretedOption(DescriptorProtos.UninterpretedOption.Builder builderForValue) The parser stores options it doesn't recognize here. See above.
repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999 [json_name = "uninterpretedOption"]; -
addUninterpretedOption
public DescriptorProtos.FieldOptions.Builder addUninterpretedOption(int index, DescriptorProtos.UninterpretedOption.Builder builderForValue) The parser stores options it doesn't recognize here. See above.
repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999 [json_name = "uninterpretedOption"]; -
addAllUninterpretedOption
public DescriptorProtos.FieldOptions.Builder addAllUninterpretedOption(Iterable<? extends DescriptorProtos.UninterpretedOption> values) The parser stores options it doesn't recognize here. See above.
repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999 [json_name = "uninterpretedOption"]; -
clearUninterpretedOption
The parser stores options it doesn't recognize here. See above.
repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999 [json_name = "uninterpretedOption"]; -
removeUninterpretedOption
The parser stores options it doesn't recognize here. See above.
repeated .google.protobuf.UninterpretedOption uninterpreted_option = 999 [json_name = "uninterpretedOption"];
-