Google.Protobuf.Reflection.FieldOptions
public sealed class FieldOptions : IExtendableMessage<FieldOptions>, IMessage<FieldOptions>, IMessage, IEquatable<FieldOptions>, IDeepCloneable<FieldOptions>, IBufferMessage
Container for nested types declared in the FieldOptions message type.
Field number for the "ctype" field.
Field number for the "debug_redact" field.
Field number for the "deprecated" field.
Field number for the "edition_defaults" field.
Field number for the "features" field.
Field number for the "feature_support" field.
Field number for the "jstype" field.
Field number for the "lazy" field.
Field number for the "packed" field.
Field number for the "retention" field.
Field number for the "targets" field.
Field number for the "uninterpreted_option" field.
Field number for the "unverified_lazy" field.
Field number for the "weak" field.
NOTE: ctype is deprecated. Use `features.(pb.cpp).string_type` instead.
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.
TODO: make ctype actually deprecated.
Indicate that the field value should not be printed out when using debug
formats, e.g. when the field contains sensitive credentials.
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.
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 "ctype" field is set
Gets whether the "debug_redact" field is set
Gets whether the "deprecated" field is set
Gets whether the "jstype" field is set
Gets whether the "lazy" field is set
Gets whether the "packed" field is set
Gets whether the "retention" field is set
Gets whether the "unverified_lazy" field is set
Gets whether the "weak" field is set
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 lazy message fields are still eagerly verified to check
ill-formed wireformat or missing required fields. Calling IsInitialized()
on the outer message would fail if the inner message has missing required
fields. Failed verification would result in parsing failure (except when
uninitialized messages are acceptable).
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. This option is prohibited in
Editions, but the `repeated_field_encoding` feature can be used to control
the behavior.
The parser stores options it doesn't recognize here. See above.
unverified_lazy does no correctness checks on the byte stream. This should
only be used where lazy with verification is prohibitive for performance
reasons.
DEPRECATED. DO NOT USE!
For Google-internal migration only. Do not use.
public FieldOptions()
Clears the value of the "ctype" field
Clears the value of the "debug_redact" field
Clears the value of the "deprecated" field
Clears the value of the "jstype" field
Clears the value of the "lazy" field
Clears the value of the "packed" field
Clears the value of the "retention" field
Clears the value of the "unverified_lazy" field
Clears the value of the "weak" field
public RepeatedField<TValue> GetExtension<TValue>(RepeatedExtension<FieldOptions, TValue> extension)
public RepeatedField<TValue> GetOrInitializeExtension<TValue>(RepeatedExtension<FieldOptions, TValue> extension)