from message google.protobuf.FieldOptions
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!
from field: optional google.protobuf.FieldOptions.CType ctype = 1 [default = STRING];
Indicate that the field value should not be printed out when using debug formats, e.g. when the field contains sensitive credentials.
from field: optional bool debug_redact = 16 [default = false];
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.
from field: optional bool deprecated = 3 [default = false];
This option is an enum to permit additional types to be added, e.g. goog.math.Integer.
from field: optional google.protobuf.FieldOptions.JSType jstype = 6 [default = JS_NORMAL];
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.
from field: optional bool lazy = 5 [default = false];
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.
from field: optional bool packed = 2;
from field: optional google.protobuf.FieldOptions.OptionRetention retention = 17;
from field: optional google.protobuf.FieldOptions.OptionTargetType target = 18 [deprecated = true];
from field: repeated google.protobuf.FieldOptions.OptionTargetType targets = 19;
The parser stores options it doesn't recognize here. See above.
from field: repeated google.protobuf.UninterpretedOption uninterpreted_option = 999;
unverified_lazy does no correctness checks on the byte stream. This should only be used where lazy with verification is prohibitive for performance reasons.
from field: optional bool unverified_lazy = 15 [default = false];
For Google-internal migration only. Do not use.
from field: optional bool weak = 10 [default = false];
Create a deep copy.
Compare with a message of the same type.
Parse a message from a JSON value.
Serialize the message to binary data.
Override for serialization behavior. This will be invoked when calling JSON.stringify on this message (i.e. JSON.stringify(msg)).
Note that this will not serialize google.protobuf.Any with a packed message because the protobuf JSON format specifies that it needs to be unpacked, and this is only possible with a type registry to look up the message type. As a result, attempting to serialize a message with this type will throw an Error.
This method is protected because you should not need to invoke it directly -- instead use JSON.stringify or toJsonString for stringified JSON. Alternatively, if actual JSON is desired, you should use toJson.
Serialize the message to a JSON string.
Generated using TypeDoc