@furo/open-models 1.15.3 → 1.16.0

package/dist/protoc-gen-open-models/google/protobuf/FieldOptions.d.ts

@@ -0,0 +1,264 @@
+import { ARRAY, BOOLEAN, ENUM, FieldNode } from '@furo/open-models/dist/index';
+import { FeatureSet as GoogleProtobufFeatureSet, type IFeatureSet as IGoogleProtobufFeatureSet, type TFeatureSet as TGoogleProtobufFeatureSet } from './FeatureSet.js';
+import { FieldOptionsCType as GoogleProtobufFieldOptionsCType } from './FieldOptions.CType.js';
+import { FieldOptionsEditionDefault as GoogleProtobufFieldOptionsEditionDefault, type IFieldOptionsEditionDefault as IGoogleProtobufFieldOptionsEditionDefault, type TFieldOptionsEditionDefault as TGoogleProtobufFieldOptionsEditionDefault } from './FieldOptions.EditionDefault.js';
+import { FieldOptionsJSType as GoogleProtobufFieldOptionsJSType } from './FieldOptions.JSType.js';
+import { FieldOptionsOptionRetention as GoogleProtobufFieldOptionsOptionRetention } from './FieldOptions.OptionRetention.js';
+import { FieldOptionsOptionTargetType as GoogleProtobufFieldOptionsOptionTargetType } from './FieldOptions.OptionTargetType.js';
+import { UninterpretedOption as GoogleProtobufUninterpretedOption, type IUninterpretedOption as IGoogleProtobufUninterpretedOption, type TUninterpretedOption as TGoogleProtobufUninterpretedOption } from './UninterpretedOption.js';
+/**
+ * @interface IFieldOptions
+ */
+export interface IFieldOptions {
+    /**
+     *  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!
+     */
+    ctype?: GoogleProtobufFieldOptionsCType | string;
+    /**
+     *  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.
+     */
+    packed?: boolean;
+    /**
+     *  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.
+     */
+    jstype?: GoogleProtobufFieldOptionsJSType | string;
+    /**
+     *  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.
+     */
+    lazy?: boolean;
+    /**
+     *  unverified_lazy does no correctness checks on the byte stream. This should
+     *  only be used where lazy with verification is prohibitive for performance
+     *  reasons.
+     */
+    unverifiedLazy?: boolean;
+    /**
+     *  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.
+     */
+    deprecated?: boolean;
+    /**
+     *  For Google-internal migration only. Do not use.
+     */
+    weak?: boolean;
+    /**
+     *  Indicate that the field value should not be printed out when using debug
+     *  formats, e.g. when the field contains sensitive credentials.
+     */
+    debugRedact?: boolean;
+    retention?: GoogleProtobufFieldOptionsOptionRetention | string;
+    targets?: GoogleProtobufFieldOptionsOptionTargetType[];
+    editionDefaults?: IGoogleProtobufFieldOptionsEditionDefault[];
+    /**
+     *  Any features defined in the specific edition.
+     */
+    features?: IGoogleProtobufFeatureSet;
+    /**
+     *  The parser stores options it doesn't recognize here. See above.
+     */
+    uninterpretedOption?: IGoogleProtobufUninterpretedOption[];
+}
+/**
+ * @interface TFieldOptions
+ */
+export interface TFieldOptions {
+    /**
+     *  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!
+     */
+    ctype?: GoogleProtobufFieldOptionsCType | string;
+    /**
+     *  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.
+     */
+    packed?: boolean;
+    /**
+     *  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.
+     */
+    jstype?: GoogleProtobufFieldOptionsJSType | string;
+    /**
+     *  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.
+     */
+    lazy?: boolean;
+    /**
+     *  unverified_lazy does no correctness checks on the byte stream. This should
+     *  only be used where lazy with verification is prohibitive for performance
+     *  reasons.
+     */
+    unverified_lazy?: boolean;
+    /**
+     *  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.
+     */
+    deprecated?: boolean;
+    /**
+     *  For Google-internal migration only. Do not use.
+     */
+    weak?: boolean;
+    /**
+     *  Indicate that the field value should not be printed out when using debug
+     *  formats, e.g. when the field contains sensitive credentials.
+     */
+    debug_redact?: boolean;
+    retention?: GoogleProtobufFieldOptionsOptionRetention | string;
+    targets?: GoogleProtobufFieldOptionsOptionTargetType[];
+    edition_defaults?: TGoogleProtobufFieldOptionsEditionDefault[];
+    /**
+     *  Any features defined in the specific edition.
+     */
+    features?: TGoogleProtobufFeatureSet;
+    /**
+     *  The parser stores options it doesn't recognize here. See above.
+     */
+    uninterpreted_option?: TGoogleProtobufUninterpretedOption[];
+}
+/**
+ * FieldOptions
+ */
+export declare class FieldOptions extends FieldNode {
+    private _ctype;
+    private _packed;
+    private _jstype;
+    private _lazy;
+    private _unverifiedLazy;
+    private _deprecated;
+    private _weak;
+    private _debugRedact;
+    private _retention;
+    private _targets;
+    private _editionDefaults;
+    private _features;
+    private _uninterpretedOption;
+    __defaultValues: IFieldOptions;
+    constructor(initData?: IFieldOptions, parent?: FieldNode, parentAttributeName?: string);
+    get ctype(): ENUM<GoogleProtobufFieldOptionsCType>;
+    set ctype(v: GoogleProtobufFieldOptionsCType);
+    get packed(): BOOLEAN;
+    set packed(v: boolean);
+    get jstype(): ENUM<GoogleProtobufFieldOptionsJSType>;
+    set jstype(v: GoogleProtobufFieldOptionsJSType);
+    get lazy(): BOOLEAN;
+    set lazy(v: boolean);
+    get unverifiedLazy(): BOOLEAN;
+    set unverifiedLazy(v: boolean);
+    get deprecated(): BOOLEAN;
+    set deprecated(v: boolean);
+    get weak(): BOOLEAN;
+    set weak(v: boolean);
+    get debugRedact(): BOOLEAN;
+    set debugRedact(v: boolean);
+    get retention(): ENUM<GoogleProtobufFieldOptionsOptionRetention>;
+    set retention(v: GoogleProtobufFieldOptionsOptionRetention);
+    get targets(): ENUM<GoogleProtobufFieldOptionsOptionTargetType>;
+    set targets(v: GoogleProtobufFieldOptionsOptionTargetType);
+    get editionDefaults(): ARRAY<GoogleProtobufFieldOptionsEditionDefault, IGoogleProtobufFieldOptionsEditionDefault>;
+    set editionDefaults(v: IGoogleProtobufFieldOptionsEditionDefault[]);
+    get features(): GoogleProtobufFeatureSet;
+    set features(v: IGoogleProtobufFeatureSet);
+    get uninterpretedOption(): ARRAY<GoogleProtobufUninterpretedOption, IGoogleProtobufUninterpretedOption>;
+    set uninterpretedOption(v: IGoogleProtobufUninterpretedOption[]);
+    fromLiteral(data: IFieldOptions): void;
+    toLiteral(): IFieldOptions;
+}

package/dist/protoc-gen-open-models/google/protobuf/FieldOptions.js

@@ -0,0 +1,364 @@
+// Code generated by furo protoc-gen-open-models. DO NOT EDIT.
+// protoc-gen-open-models version: ????
+import { ARRAY, BOOLEAN, ENUM, FieldNode, Registry, } from '@furo/open-models/dist/index';
+import { FeatureSet as GoogleProtobufFeatureSet, } from './FeatureSet.js';
+import { FieldOptionsCType as GoogleProtobufFieldOptionsCType } from './FieldOptions.CType.js';
+import { FieldOptionsEditionDefault as GoogleProtobufFieldOptionsEditionDefault, } from './FieldOptions.EditionDefault.js';
+import { FieldOptionsJSType as GoogleProtobufFieldOptionsJSType } from './FieldOptions.JSType.js';
+import { FieldOptionsOptionRetention as GoogleProtobufFieldOptionsOptionRetention } from './FieldOptions.OptionRetention.js';
+import { FieldOptionsOptionTargetType as GoogleProtobufFieldOptionsOptionTargetType } from './FieldOptions.OptionTargetType.js';
+import { UninterpretedOption as GoogleProtobufUninterpretedOption, } from './UninterpretedOption.js';
+/**
+ * FieldOptions
+ */
+export class FieldOptions extends FieldNode {
+    constructor(initData, parent, parentAttributeName) {
+        super(undefined, parent, parentAttributeName);
+        this.__meta.typeName = 'google.protobuf.FieldOptions';
+        this.__meta.description = 'FieldOptions';
+        this.__meta.nodeFields = [
+            {
+                fieldName: 'ctype',
+                protoName: 'ctype',
+                FieldConstructor: (ENUM),
+                constraints: {},
+                description: 'The ctype option instructs the C++ code generator to use a different\n representation of the field than it normally would.  See the specific\n options below.  This option is only implemented to support use of\n [ctype=CORD] and [ctype=STRING] (the default) on non-repeated fields of\n type "bytes" in the open source release -- sorry, we\'ll try to include\n other types in a future version!',
+            },
+            {
+                fieldName: 'packed',
+                protoName: 'packed',
+                FieldConstructor: BOOLEAN,
+                constraints: {},
+                description: 'The packed option can be enabled for repeated primitive fields to enable\n a more efficient representation on the wire. Rather than repeatedly\n writing the tag and type for each element, the entire array is encoded as\n a single length-delimited blob. In proto3, only explicit setting it to\n false will avoid using packed encoding.  This option is prohibited in\n Editions, but the `repeated_field_encoding` feature can be used to control\n the behavior.',
+            },
+            {
+                fieldName: 'jstype',
+                protoName: 'jstype',
+                FieldConstructor: (ENUM),
+                constraints: {},
+                description: 'The jstype option determines the JavaScript type used for values of the\n field.  The option is permitted only for 64 bit integral and fixed types\n (int64, uint64, sint64, fixed64, sfixed64).  A field with jstype JS_STRING\n is represented as JavaScript string, which avoids loss of precision that\n can happen when a large value is converted to a floating point JavaScript.\n Specifying JS_NUMBER for the jstype causes the generated JavaScript code to\n use the JavaScript "number" type.  The behavior of the default option\n JS_NORMAL is implementation dependent.\n\n This option is an enum to permit additional types to be added, e.g.\n goog.math.Integer.',
+            },
+            {
+                fieldName: 'lazy',
+                protoName: 'lazy',
+                FieldConstructor: BOOLEAN,
+                constraints: {},
+                description: "Should this field be parsed lazily?  Lazy applies only to message-type\n fields.  It means that when the outer message is initially parsed, the\n inner message's contents will not be parsed but instead stored in encoded\n form.  The inner message will actually be parsed when it is first accessed.\n\n This is only a hint.  Implementations are free to choose whether to use\n eager or lazy parsing regardless of the value of this option.  However,\n setting this option true suggests that the protocol author believes that\n using lazy parsing on this field is worth the additional bookkeeping\n overhead typically needed to implement it.\n\n This option does not affect the public interface of any generated code;\n all method signatures remain the same.  Furthermore, thread-safety of the\n interface is not affected by this option; const methods remain safe to\n call from multiple threads concurrently, while non-const methods continue\n to require exclusive access.\n\n Note that implementations may choose not to check required fields within\n a lazy sub-message.  That is, calling IsInitialized() on the outer message\n may return true even if the inner message has missing required fields.\n This is necessary because otherwise the inner message would have to be\n parsed in order to perform the check, defeating the purpose of lazy\n parsing.  An implementation which chooses not to check required fields\n must be consistent about it.  That is, for any particular sub-message, the\n implementation must either *always* check its required fields, or *never*\n check its required fields, regardless of whether or not the message has\n been parsed.\n\n As of May 2022, lazy verifies the contents of the byte stream during\n parsing.  An invalid byte stream will cause the overall parsing to fail.",
+            },
+            {
+                fieldName: 'unverifiedLazy',
+                protoName: 'unverified_lazy',
+                FieldConstructor: BOOLEAN,
+                constraints: {},
+                description: 'unverified_lazy does no correctness checks on the byte stream. This should\n only be used where lazy with verification is prohibitive for performance\n reasons.',
+            },
+            {
+                fieldName: 'deprecated',
+                protoName: 'deprecated',
+                FieldConstructor: BOOLEAN,
+                constraints: {},
+                description: 'Is this field deprecated?\n Depending on the target platform, this can emit Deprecated annotations\n for accessors, or it will be completely ignored; in the very least, this\n is a formalization for deprecating fields.',
+            },
+            {
+                fieldName: 'weak',
+                protoName: 'weak',
+                FieldConstructor: BOOLEAN,
+                constraints: {},
+                description: 'For Google-internal migration only. Do not use.',
+            },
+            {
+                fieldName: 'debugRedact',
+                protoName: 'debug_redact',
+                FieldConstructor: BOOLEAN,
+                constraints: {},
+                description: 'Indicate that the field value should not be printed out when using debug\n formats, e.g. when the field contains sensitive credentials.',
+            },
+            {
+                fieldName: 'retention',
+                protoName: 'retention',
+                FieldConstructor: (ENUM),
+                constraints: {},
+                description: '',
+            },
+            {
+                fieldName: 'targets',
+                protoName: 'targets',
+                FieldConstructor: (ENUM),
+                constraints: {},
+                description: '',
+            },
+            {
+                fieldName: 'editionDefaults',
+                protoName: 'edition_defaults',
+                FieldConstructor: GoogleProtobufFieldOptionsEditionDefault,
+                constraints: {},
+                description: '',
+            },
+            {
+                fieldName: 'features',
+                protoName: 'features',
+                FieldConstructor: GoogleProtobufFeatureSet,
+                constraints: {},
+                description: 'Any features defined in the specific edition.',
+            },
+            {
+                fieldName: 'uninterpretedOption',
+                protoName: 'uninterpreted_option',
+                FieldConstructor: GoogleProtobufUninterpretedOption,
+                constraints: {},
+                description: "The parser stores options it doesn't recognize here. See above.",
+            },
+        ];
+        // Initialize the fields
+        //  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!
+        this._ctype = new ENUM(undefined, GoogleProtobufFieldOptionsCType, GoogleProtobufFieldOptionsCType.STRING, this, 'ctype');
+        //  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.
+        this._packed = new BOOLEAN(undefined, this, 'packed');
+        //  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.
+        this._jstype = new ENUM(undefined, GoogleProtobufFieldOptionsJSType, GoogleProtobufFieldOptionsJSType.JS_NORMAL, this, 'jstype');
+        //  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.
+        this._lazy = new BOOLEAN(undefined, this, 'lazy');
+        //  unverified_lazy does no correctness checks on the byte stream. This should
+        //  only be used where lazy with verification is prohibitive for performance
+        //  reasons.
+        this._unverifiedLazy = new BOOLEAN(undefined, this, 'unverifiedLazy');
+        //  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.
+        this._deprecated = new BOOLEAN(undefined, this, 'deprecated');
+        //  For Google-internal migration only. Do not use.
+        this._weak = new BOOLEAN(undefined, this, 'weak');
+        //  Indicate that the field value should not be printed out when using debug
+        //  formats, e.g. when the field contains sensitive credentials.
+        this._debugRedact = new BOOLEAN(undefined, this, 'debugRedact');
+        this._retention = new ENUM(undefined, GoogleProtobufFieldOptionsOptionRetention, GoogleProtobufFieldOptionsOptionRetention.RETENTION_UNKNOWN, this, 'retention');
+        this._targets = new ENUM(undefined, GoogleProtobufFieldOptionsOptionTargetType, GoogleProtobufFieldOptionsOptionTargetType.TARGET_TYPE_UNKNOWN, this, 'targets');
+        this._editionDefaults = new ARRAY(undefined, this, 'editionDefaults');
+        //  Any features defined in the specific edition.
+        this._features = new GoogleProtobufFeatureSet(undefined, this, 'features');
+        //  The parser stores options it doesn't recognize here. See above.
+        this._uninterpretedOption = new ARRAY(undefined, this, 'uninterpretedOption');
+        // Set required fields
+        [].forEach(fieldName => {
+            this[fieldName].__meta.required =
+                true;
+        });
+        // Default values from openAPI annotations
+        this.__defaultValues = {};
+        // Initialize the fields with init data
+        if (initData !== undefined) {
+            this.__fromLiteral({ ...this.__defaultValues, ...initData });
+        }
+        else {
+            this.__fromLiteral(this.__defaultValues);
+        }
+        // Set readonly fields after the init, so child nodes are readonly too
+        [].forEach(fieldName => {
+            this[fieldName].__readonly = true;
+        });
+        this.__meta.isPristine = true;
+    }
+    //  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!
+    get ctype() {
+        return this._ctype;
+    }
+    set ctype(v) {
+        this.__TypeSetter(this._ctype, v);
+    }
+    //  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.
+    get packed() {
+        return this._packed;
+    }
+    set packed(v) {
+        this.__PrimitivesSetter(this._packed, v);
+    }
+    //  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.
+    get jstype() {
+        return this._jstype;
+    }
+    set jstype(v) {
+        this.__TypeSetter(this._jstype, v);
+    }
+    //  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.
+    get lazy() {
+        return this._lazy;
+    }
+    set lazy(v) {
+        this.__PrimitivesSetter(this._lazy, v);
+    }
+    //  unverified_lazy does no correctness checks on the byte stream. This should
+    //  only be used where lazy with verification is prohibitive for performance
+    //  reasons.
+    get unverifiedLazy() {
+        return this._unverifiedLazy;
+    }
+    set unverifiedLazy(v) {
+        this.__PrimitivesSetter(this._unverifiedLazy, v);
+    }
+    //  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.
+    get deprecated() {
+        return this._deprecated;
+    }
+    set deprecated(v) {
+        this.__PrimitivesSetter(this._deprecated, v);
+    }
+    //  For Google-internal migration only. Do not use.
+    get weak() {
+        return this._weak;
+    }
+    set weak(v) {
+        this.__PrimitivesSetter(this._weak, v);
+    }
+    //  Indicate that the field value should not be printed out when using debug
+    //  formats, e.g. when the field contains sensitive credentials.
+    get debugRedact() {
+        return this._debugRedact;
+    }
+    set debugRedact(v) {
+        this.__PrimitivesSetter(this._debugRedact, v);
+    }
+    get retention() {
+        return this._retention;
+    }
+    set retention(v) {
+        this.__TypeSetter(this._retention, v);
+    }
+    get targets() {
+        return this._targets;
+    }
+    set targets(v) {
+        this.__TypeSetter(this._targets, v);
+    }
+    get editionDefaults() {
+        return this._editionDefaults;
+    }
+    set editionDefaults(v) {
+        this.__TypeSetter(this._editionDefaults, v);
+    }
+    //  Any features defined in the specific edition.
+    get features() {
+        return this._features;
+    }
+    set features(v) {
+        this.__TypeSetter(this._features, v);
+    }
+    //  The parser stores options it doesn't recognize here. See above.
+    get uninterpretedOption() {
+        return this._uninterpretedOption;
+    }
+    set uninterpretedOption(v) {
+        this.__TypeSetter(this._uninterpretedOption, v);
+    }
+    fromLiteral(data) {
+        super.__fromLiteral(data);
+    }
+    toLiteral() {
+        return super.__toLiteral();
+    }
+}
+Registry.register('google.protobuf.FieldOptions', FieldOptions);
+//# sourceMappingURL=FieldOptions.js.map