juno-network 0.12.0 → 0.14.0

package/src/codegen/google/protobuf/descriptor.ts

@@ -48,54 +48,7 @@ export enum FieldDescriptorProto_Type {
   TYPE_SINT64 = 18,
   UNRECOGNIZED = -1,
 }
-export enum FieldDescriptorProto_TypeSDKType {
-  /**
-   * TYPE_DOUBLE - 0 is reserved for errors.
-   * Order is weird for historical reasons.
-   */
-  TYPE_DOUBLE = 1,
-  TYPE_FLOAT = 2,
-
-  /**
-   * TYPE_INT64 - Not ZigZag encoded.  Negative numbers take 10 bytes.  Use TYPE_SINT64 if
-   * negative values are likely.
-   */
-  TYPE_INT64 = 3,
-  TYPE_UINT64 = 4,
-
-  /**
-   * TYPE_INT32 - Not ZigZag encoded.  Negative numbers take 10 bytes.  Use TYPE_SINT32 if
-   * negative values are likely.
-   */
-  TYPE_INT32 = 5,
-  TYPE_FIXED64 = 6,
-  TYPE_FIXED32 = 7,
-  TYPE_BOOL = 8,
-  TYPE_STRING = 9,
-
-  /**
-   * TYPE_GROUP - Tag-delimited aggregate.
-   * Group type is deprecated and not supported in proto3. However, Proto3
-   * implementations should still be able to parse the group wire format and
-   * treat group fields as unknown fields.
-   */
-  TYPE_GROUP = 10,
-  TYPE_MESSAGE = 11,
-
-  /** TYPE_BYTES - New in version 2. */
-  TYPE_BYTES = 12,
-  TYPE_UINT32 = 13,
-  TYPE_ENUM = 14,
-  TYPE_SFIXED32 = 15,
-  TYPE_SFIXED64 = 16,
-
-  /** TYPE_SINT32 - Uses ZigZag encoding. */
-  TYPE_SINT32 = 17,
-
-  /** TYPE_SINT64 - Uses ZigZag encoding. */
-  TYPE_SINT64 = 18,
-  UNRECOGNIZED = -1,
-}
+export const FieldDescriptorProto_TypeSDKType = FieldDescriptorProto_Type;
 export function fieldDescriptorProto_TypeFromJSON(object: any): FieldDescriptorProto_Type {
   switch (object) {
     case 1:
@@ -244,13 +197,7 @@ export enum FieldDescriptorProto_Label {
   LABEL_REPEATED = 3,
   UNRECOGNIZED = -1,
 }
-export enum FieldDescriptorProto_LabelSDKType {
-  /** LABEL_OPTIONAL - 0 is reserved for errors */
-  LABEL_OPTIONAL = 1,
-  LABEL_REQUIRED = 2,
-  LABEL_REPEATED = 3,
-  UNRECOGNIZED = -1,
-}
+export const FieldDescriptorProto_LabelSDKType = FieldDescriptorProto_Label;
 export function fieldDescriptorProto_LabelFromJSON(object: any): FieldDescriptorProto_Label {
   switch (object) {
     case 1:
@@ -303,22 +250,7 @@ export enum FileOptions_OptimizeMode {
   LITE_RUNTIME = 3,
   UNRECOGNIZED = -1,
 }
-/** Generated classes can be optimized for speed or code size. */
-
-export enum FileOptions_OptimizeModeSDKType {
-  /**
-   * SPEED - Generate complete code for parsing, serialization,
-   * etc.
-   */
-  SPEED = 1,
-
-  /** CODE_SIZE - Use ReflectionOps to implement these methods. */
-  CODE_SIZE = 2,
-
-  /** LITE_RUNTIME - Generate code using MessageLite and the lite runtime. */
-  LITE_RUNTIME = 3,
-  UNRECOGNIZED = -1,
-}
+export const FileOptions_OptimizeModeSDKType = FileOptions_OptimizeMode;
 export function fileOptions_OptimizeModeFromJSON(object: any): FileOptions_OptimizeMode {
   switch (object) {
     case 1:
@@ -362,13 +294,7 @@ export enum FieldOptions_CType {
   STRING_PIECE = 2,
   UNRECOGNIZED = -1,
 }
-export enum FieldOptions_CTypeSDKType {
-  /** STRING - Default mode. */
-  STRING = 0,
-  CORD = 1,
-  STRING_PIECE = 2,
-  UNRECOGNIZED = -1,
-}
+export const FieldOptions_CTypeSDKType = FieldOptions_CType;
 export function fieldOptions_CTypeFromJSON(object: any): FieldOptions_CType {
   switch (object) {
     case 0:
@@ -416,17 +342,7 @@ export enum FieldOptions_JSType {
   JS_NUMBER = 2,
   UNRECOGNIZED = -1,
 }
-export enum FieldOptions_JSTypeSDKType {
-  /** JS_NORMAL - Use the default type. */
-  JS_NORMAL = 0,
-
-  /** JS_STRING - Use JavaScript strings. */
-  JS_STRING = 1,
-
-  /** JS_NUMBER - Use JavaScript numbers. */
-  JS_NUMBER = 2,
-  UNRECOGNIZED = -1,
-}
+export const FieldOptions_JSTypeSDKType = FieldOptions_JSType;
 export function fieldOptions_JSTypeFromJSON(object: any): FieldOptions_JSType {
   switch (object) {
     case 0:
@@ -479,22 +395,7 @@ export enum MethodOptions_IdempotencyLevel {
   IDEMPOTENT = 2,
   UNRECOGNIZED = -1,
 }
-/**
- * Is this method side-effect-free (or safe in HTTP parlance), or idempotent,
- * or neither? HTTP based RPC implementation may choose GET verb for safe
- * methods, and PUT verb for idempotent methods instead of the default POST.
- */
-
-export enum MethodOptions_IdempotencyLevelSDKType {
-  IDEMPOTENCY_UNKNOWN = 0,
-
-  /** NO_SIDE_EFFECTS - implies idempotent */
-  NO_SIDE_EFFECTS = 1,
-
-  /** IDEMPOTENT - idempotent, but may have side effects */
-  IDEMPOTENT = 2,
-  UNRECOGNIZED = -1,
-}
+export const MethodOptions_IdempotencyLevelSDKType = MethodOptions_IdempotencyLevel;
 export function methodOptions_IdempotencyLevelFromJSON(object: any): MethodOptions_IdempotencyLevel {
   switch (object) {
     case 0:
@@ -590,41 +491,17 @@ export interface FileDescriptorProto {
 /** Describes a complete .proto file. */
 
 export interface FileDescriptorProtoSDKType {
-  /** file name, relative to root of source tree */
   name: string;
   package: string;
-  /** Names of files imported by this file. */
-
   dependency: string[];
-  /** Indexes of the public imported files in the dependency list above. */
-
   public_dependency: number[];
-  /**
-   * Indexes of the weak imported files in the dependency list.
-   * For Google-internal migration only. Do not use.
-   */
-
   weak_dependency: number[];
-  /** All top-level definitions in this file. */
-
   message_type: DescriptorProtoSDKType[];
   enum_type: EnumDescriptorProtoSDKType[];
   service: ServiceDescriptorProtoSDKType[];
   extension: FieldDescriptorProtoSDKType[];
   options?: FileOptionsSDKType;
-  /**
-   * This field contains optional information about the original source code.
-   * You may safely remove this entire field without harming runtime
-   * functionality of the descriptors -- the information is needed only by
-   * development tools.
-   */
-
   source_code_info?: SourceCodeInfoSDKType;
-  /**
-   * The syntax of the proto file.
-   * The supported values are "proto2" and "proto3".
-   */
-
   syntax: string;
 }
 /** Describes a message type. */
@@ -658,11 +535,6 @@ export interface DescriptorProtoSDKType {
   oneof_decl: OneofDescriptorProtoSDKType[];
   options?: MessageOptionsSDKType;
   reserved_range: DescriptorProto_ReservedRangeSDKType[];
-  /**
-   * Reserved field names, which may not be used by fields in the same message.
-   * A given name may only be reserved once.
-   */
-
   reserved_name: string[];
 }
 export interface DescriptorProto_ExtensionRange {
@@ -674,10 +546,7 @@ export interface DescriptorProto_ExtensionRange {
   options?: ExtensionRangeOptions;
 }
 export interface DescriptorProto_ExtensionRangeSDKType {
-  /** Inclusive. */
   start: number;
-  /** Exclusive. */
-
   end: number;
   options?: ExtensionRangeOptionsSDKType;
 }
@@ -701,10 +570,7 @@ export interface DescriptorProto_ReservedRange {
  */
 
 export interface DescriptorProto_ReservedRangeSDKType {
-  /** Inclusive. */
   start: number;
-  /** Exclusive. */
-
   end: number;
 }
 export interface ExtensionRangeOptions {
@@ -712,7 +578,6 @@ export interface ExtensionRangeOptions {
   uninterpretedOption: UninterpretedOption[];
 }
 export interface ExtensionRangeOptionsSDKType {
-  /** The parser stores options it doesn't recognize here. See above. */
   uninterpreted_option: UninterpretedOptionSDKType[];
 }
 /** Describes a field within a message. */
@@ -772,50 +637,12 @@ export interface FieldDescriptorProto {
 export interface FieldDescriptorProtoSDKType {
   name: string;
   number: number;
-  label: FieldDescriptorProto_LabelSDKType;
-  /**
-   * If type_name is set, this need not be set.  If both this and type_name
-   * are set, this must be one of TYPE_ENUM, TYPE_MESSAGE or TYPE_GROUP.
-   */
-
-  type: FieldDescriptorProto_TypeSDKType;
-  /**
-   * For message and enum types, this is the name of the type.  If the name
-   * starts with a '.', it is fully-qualified.  Otherwise, C++-like scoping
-   * rules are used to find the type (i.e. first the nested types within this
-   * message are searched, then within the parent, on up to the root
-   * namespace).
-   */
-
+  label: FieldDescriptorProto_Label;
+  type: FieldDescriptorProto_Type;
   type_name: string;
-  /**
-   * For extensions, this is the name of the type being extended.  It is
-   * resolved in the same manner as type_name.
-   */
-
   extendee: string;
-  /**
-   * For numeric types, contains the original text representation of the value.
-   * For booleans, "true" or "false".
-   * For strings, contains the default text contents (not escaped in any way).
-   * For bytes, contains the C escaped value.  All bytes >= 128 are escaped.
-   * TODO(kenton):  Base-64 encode?
-   */
-
   default_value: string;
-  /**
-   * If set, gives the index of a oneof in the containing type's oneof_decl
-   * list.  This field is a member of that oneof.
-   */
-
   oneof_index: number;
-  /**
-   * JSON name of this field. The value is set by protocol compiler. If the
-   * user has set a "json_name" option on this field, that option's value
-   * will be used. Otherwise, it's deduced from the field's name by converting
-   * it to camelCase.
-   */
-
   json_name: string;
   options?: FieldOptionsSDKType;
 }
@@ -857,18 +684,7 @@ export interface EnumDescriptorProtoSDKType {
   name: string;
   value: EnumValueDescriptorProtoSDKType[];
   options?: EnumOptionsSDKType;
-  /**
-   * Range of reserved numeric values. Reserved numeric values may not be used
-   * by enum values in the same enum declaration. Reserved ranges may not
-   * overlap.
-   */
-
   reserved_range: EnumDescriptorProto_EnumReservedRangeSDKType[];
-  /**
-   * Reserved enum value names, which may not be reused. A given name may only
-   * be reserved once.
-   */
-
   reserved_name: string[];
 }
 /**
@@ -897,10 +713,7 @@ export interface EnumDescriptorProto_EnumReservedRange {
  */
 
 export interface EnumDescriptorProto_EnumReservedRangeSDKType {
-  /** Inclusive. */
   start: number;
-  /** Inclusive. */
-
   end: number;
 }
 /** Describes a value within an enum. */
@@ -954,19 +767,10 @@ export interface MethodDescriptorProto {
 
 export interface MethodDescriptorProtoSDKType {
   name: string;
-  /**
-   * Input and output type names.  These are resolved in the same way as
-   * FieldDescriptorProto.type_name, but must refer to a message type.
-   */
-
   input_type: string;
   output_type: string;
   options?: MethodOptionsSDKType;
-  /** Identifies if client streams multiple client messages */
-
   client_streaming: boolean;
-  /** Identifies if server streams multiple server messages */
-
   server_streaming: boolean;
 }
 export interface FileOptions {
@@ -1104,137 +908,28 @@ export interface FileOptions {
   uninterpretedOption: UninterpretedOption[];
 }
 export interface FileOptionsSDKType {
-  /**
-   * Sets the Java package where classes generated from this .proto will be
-   * placed.  By default, the proto package is used, but this is often
-   * inappropriate because proto packages do not normally start with backwards
-   * domain names.
-   */
   java_package: string;
-  /**
-   * If set, all the classes from the .proto file are wrapped in a single
-   * outer class with the given name.  This applies to both Proto1
-   * (equivalent to the old "--one_java_file" option) and Proto2 (where
-   * a .proto always translates to a single class, but you may want to
-   * explicitly choose the class name).
-   */
-
   java_outer_classname: string;
-  /**
-   * If set true, then the Java code generator will generate a separate .java
-   * file for each top-level message, enum, and service defined in the .proto
-   * file.  Thus, these types will *not* be nested inside the outer class
-   * named by java_outer_classname.  However, the outer class will still be
-   * generated to contain the file's getDescriptor() method as well as any
-   * top-level extensions defined in the file.
-   */
-
   java_multiple_files: boolean;
-  /** This option does nothing. */
-
   /** @deprecated */
 
   java_generate_equals_and_hash: boolean;
-  /**
-   * If set true, then the Java2 code generator will generate code that
-   * throws an exception whenever an attempt is made to assign a non-UTF-8
-   * byte sequence to a string field.
-   * Message reflection will do the same.
-   * However, an extension field still accepts non-UTF-8 byte sequences.
-   * This option has no effect on when used with the lite runtime.
-   */
-
   java_string_check_utf8: boolean;
-  optimize_for: FileOptions_OptimizeModeSDKType;
-  /**
-   * Sets the Go package where structs generated from this .proto will be
-   * placed. If omitted, the Go package will be derived from the following:
-   *   - The basename of the package import path, if provided.
-   *   - Otherwise, the package statement in the .proto file, if present.
-   *   - Otherwise, the basename of the .proto file, without extension.
-   */
-
+  optimize_for: FileOptions_OptimizeMode;
   go_package: string;
-  /**
-   * Should generic services be generated in each language?  "Generic" services
-   * are not specific to any particular RPC system.  They are generated by the
-   * main code generators in each language (without additional plugins).
-   * Generic services were the only kind of service generation supported by
-   * early versions of google.protobuf.
-   * 
-   * Generic services are now considered deprecated in favor of using plugins
-   * that generate code specific to your particular RPC system.  Therefore,
-   * these default to false.  Old code which depends on generic services should
-   * explicitly set them to true.
-   */
-
   cc_generic_services: boolean;
   java_generic_services: boolean;
   py_generic_services: boolean;
   php_generic_services: boolean;
-  /**
-   * Is this file deprecated?
-   * Depending on the target platform, this can emit Deprecated annotations
-   * for everything in the file, or it will be completely ignored; in the very
-   * least, this is a formalization for deprecating files.
-   */
-
   deprecated: boolean;
-  /**
-   * Enables the use of arenas for the proto messages in this file. This applies
-   * only to generated classes for C++.
-   */
-
   cc_enable_arenas: boolean;
-  /**
-   * Sets the objective c class prefix which is prepended to all objective c
-   * generated classes from this .proto. There is no default.
-   */
-
   objc_class_prefix: string;
-  /** Namespace for generated classes; defaults to the package. */
-
   csharp_namespace: string;
-  /**
-   * By default Swift generators will take the proto package and CamelCase it
-   * replacing '.' with underscore and use that to prefix the types/symbols
-   * defined. When this options is provided, they will use this value instead
-   * to prefix the types/symbols defined.
-   */
-
   swift_prefix: string;
-  /**
-   * Sets the php class prefix which is prepended to all php generated classes
-   * from this .proto. Default is empty.
-   */
-
   php_class_prefix: string;
-  /**
-   * Use this option to change the namespace of php generated classes. Default
-   * is empty. When this option is empty, the package name will be used for
-   * determining the namespace.
-   */
-
   php_namespace: string;
-  /**
-   * Use this option to change the namespace of php generated metadata classes.
-   * Default is empty. When this option is empty, the proto file name will be
-   * used for determining the namespace.
-   */
-
   php_metadata_namespace: string;
-  /**
-   * Use this option to change the package of ruby generated classes. Default
-   * is empty. When this option is not set, the package name will be used for
-   * determining the ruby package.
-   */
-
   ruby_package: string;
-  /**
-   * The parser stores options it doesn't recognize here.
-   * See the documentation for the "Options" section above.
-   */
-
   uninterpreted_option: UninterpretedOptionSDKType[];
 }
 export interface MessageOptions {
@@ -1304,69 +999,10 @@ export interface MessageOptions {
   uninterpretedOption: UninterpretedOption[];
 }
 export interface MessageOptionsSDKType {
-  /**
-   * 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.
-   */
   message_set_wire_format: boolean;
-  /**
-   * 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".
-   */
-
   no_standard_descriptor_accessor: boolean;
-  /**
-   * 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.
-   */
-
   deprecated: boolean;
-  /**
-   * 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.
-   */
-
   map_entry: boolean;
-  /** The parser stores options it doesn't recognize here. See above. */
-
   uninterpreted_option: UninterpretedOptionSDKType[];
 }
 export interface FieldOptions {
@@ -1449,82 +1085,12 @@ export interface FieldOptions {
   uninterpretedOption: UninterpretedOption[];
 }
 export interface FieldOptionsSDKType {
-  /**
-   * 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 not yet implemented in the open source
-   * release -- sorry, we'll try to include it in a future version!
-   */
-  ctype: FieldOptions_CTypeSDKType;
-  /**
-   * 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.
-   */
-
+  ctype: FieldOptions_CType;
   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: FieldOptions_JSTypeSDKType;
-  /**
-   * 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.
-   */
-
+  jstype: FieldOptions_JSType;
   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;
-  /** The parser stores options it doesn't recognize here. See above. */
-
   uninterpreted_option: UninterpretedOptionSDKType[];
 }
 export interface OneofOptions {
@@ -1532,7 +1098,6 @@ export interface OneofOptions {
   uninterpretedOption: UninterpretedOption[];
 }
 export interface OneofOptionsSDKType {
-  /** The parser stores options it doesn't recognize here. See above. */
   uninterpreted_option: UninterpretedOptionSDKType[];
 }
 export interface EnumOptions {
@@ -1554,21 +1119,8 @@ export interface EnumOptions {
   uninterpretedOption: UninterpretedOption[];
 }
 export interface EnumOptionsSDKType {
-  /**
-   * Set this option to true to allow mapping different tag names to the same
-   * value.
-   */
   allow_alias: boolean;
-  /**
-   * Is this enum deprecated?
-   * Depending on the target platform, this can emit Deprecated annotations
-   * for the enum, or it will be completely ignored; in the very least, this
-   * is a formalization for deprecating enums.
-   */
-
   deprecated: boolean;
-  /** The parser stores options it doesn't recognize here. See above. */
-
   uninterpreted_option: UninterpretedOptionSDKType[];
 }
 export interface EnumValueOptions {
@@ -1584,15 +1136,7 @@ export interface EnumValueOptions {
   uninterpretedOption: UninterpretedOption[];
 }
 export interface EnumValueOptionsSDKType {
-  /**
-   * Is this enum value deprecated?
-   * Depending on the target platform, this can emit Deprecated annotations
-   * for the enum value, or it will be completely ignored; in the very least,
-   * this is a formalization for deprecating enum values.
-   */
   deprecated: boolean;
-  /** The parser stores options it doesn't recognize here. See above. */
-
   uninterpreted_option: UninterpretedOptionSDKType[];
 }
 export interface ServiceOptions {
@@ -1608,15 +1152,7 @@ export interface ServiceOptions {
   uninterpretedOption: UninterpretedOption[];
 }
 export interface ServiceOptionsSDKType {
-  /**
-   * Is this service deprecated?
-   * Depending on the target platform, this can emit Deprecated annotations
-   * for the service, or it will be completely ignored; in the very least,
-   * this is a formalization for deprecating services.
-   */
   deprecated: boolean;
-  /** The parser stores options it doesn't recognize here. See above. */
-
   uninterpreted_option: UninterpretedOptionSDKType[];
 }
 export interface MethodOptions {
@@ -1633,16 +1169,8 @@ export interface MethodOptions {
   uninterpretedOption: UninterpretedOption[];
 }
 export interface MethodOptionsSDKType {
-  /**
-   * Is this method deprecated?
-   * Depending on the target platform, this can emit Deprecated annotations
-   * for the method, or it will be completely ignored; in the very least,
-   * this is a formalization for deprecating methods.
-   */
   deprecated: boolean;
-  idempotency_level: MethodOptions_IdempotencyLevelSDKType;
-  /** The parser stores options it doesn't recognize here. See above. */
-
+  idempotency_level: MethodOptions_IdempotencyLevel;
   uninterpreted_option: UninterpretedOptionSDKType[];
 }
 /**
@@ -1679,11 +1207,6 @@ export interface UninterpretedOption {
 
 export interface UninterpretedOptionSDKType {
   name: UninterpretedOption_NamePartSDKType[];
-  /**
-   * The value of the uninterpreted option, in whatever type the tokenizer
-   * identified it as during parsing. Exactly one of these should be set.
-   */
-
   identifier_value: string;
   positive_int_value: Long;
   negative_int_value: Long;
@@ -1774,51 +1297,6 @@ export interface SourceCodeInfo {
  */
 
 export interface SourceCodeInfoSDKType {
-  /**
-   * A Location identifies a piece of source code in a .proto file which
-   * corresponds to a particular definition.  This information is intended
-   * to be useful to IDEs, code indexers, documentation generators, and similar
-   * tools.
-   * 
-   * For example, say we have a file like:
-   *   message Foo {
-   *     optional string foo = 1;
-   *   }
-   * Let's look at just the field definition:
-   *   optional string foo = 1;
-   *   ^       ^^     ^^  ^  ^^^
-   *   a       bc     de  f  ghi
-   * We have the following locations:
-   *   span   path               represents
-   *   [a,i)  [ 4, 0, 2, 0 ]     The whole field definition.
-   *   [a,b)  [ 4, 0, 2, 0, 4 ]  The label (optional).
-   *   [c,d)  [ 4, 0, 2, 0, 5 ]  The type (string).
-   *   [e,f)  [ 4, 0, 2, 0, 1 ]  The name (foo).
-   *   [g,h)  [ 4, 0, 2, 0, 3 ]  The number (1).
-   * 
-   * Notes:
-   * - A location may refer to a repeated field itself (i.e. not to any
-   *   particular index within it).  This is used whenever a set of elements are
-   *   logically enclosed in a single code segment.  For example, an entire
-   *   extend block (possibly containing multiple extension definitions) will
-   *   have an outer location whose path refers to the "extensions" repeated
-   *   field without an index.
-   * - Multiple locations may have the same path.  This happens when a single
-   *   logical declaration is spread out across multiple places.  The most
-   *   obvious example is the "extend" block again -- there may be multiple
-   *   extend blocks in the same scope, each of which will have the same path.
-   * - A location's span is not always a subset of its parent's span.  For
-   *   example, the "extendee" of an extension declaration appears at the
-   *   beginning of the "extend" block and is shared by all extensions within
-   *   the block.
-   * - Just because a location's span is a subset of some other location's span
-   *   does not mean that it is a descendant.  For example, a "group" defines
-   *   both a type and a field in a single declaration.  Thus, the locations
-   *   corresponding to the type and field and their components will overlap.
-   * - Code which tries to interpret locations should probably be designed to
-   *   ignore those that it doesn't understand, as more types of locations could
-   *   be recorded in the future.
-   */
   location: SourceCodeInfo_LocationSDKType[];
 }
 export interface SourceCodeInfo_Location {
@@ -1912,91 +1390,8 @@ export interface SourceCodeInfo_Location {
   leadingDetachedComments: string[];
 }
 export interface SourceCodeInfo_LocationSDKType {
-  /**
-   * Identifies which part of the FileDescriptorProto was defined at this
-   * location.
-   * 
-   * Each element is a field number or an index.  They form a path from
-   * the root FileDescriptorProto to the place where the definition.  For
-   * example, this path:
-   *   [ 4, 3, 2, 7, 1 ]
-   * refers to:
-   *   file.message_type(3)  // 4, 3
-   *       .field(7)         // 2, 7
-   *       .name()           // 1
-   * This is because FileDescriptorProto.message_type has field number 4:
-   *   repeated DescriptorProto message_type = 4;
-   * and DescriptorProto.field has field number 2:
-   *   repeated FieldDescriptorProto field = 2;
-   * and FieldDescriptorProto.name has field number 1:
-   *   optional string name = 1;
-   * 
-   * Thus, the above path gives the location of a field name.  If we removed
-   * the last element:
-   *   [ 4, 3, 2, 7 ]
-   * this path refers to the whole field declaration (from the beginning
-   * of the label to the terminating semicolon).
-   */
   path: number[];
-  /**
-   * Always has exactly three or four elements: start line, start column,
-   * end line (optional, otherwise assumed same as start line), end column.
-   * These are packed into a single field for efficiency.  Note that line
-   * and column numbers are zero-based -- typically you will want to add
-   * 1 to each before displaying to a user.
-   */
-
   span: number[];
-  /**
-   * If this SourceCodeInfo represents a complete declaration, these are any
-   * comments appearing before and after the declaration which appear to be
-   * attached to the declaration.
-   * 
-   * A series of line comments appearing on consecutive lines, with no other
-   * tokens appearing on those lines, will be treated as a single comment.
-   * 
-   * leading_detached_comments will keep paragraphs of comments that appear
-   * before (but not connected to) the current element. Each paragraph,
-   * separated by empty lines, will be one comment element in the repeated
-   * field.
-   * 
-   * Only the comment content is provided; comment markers (e.g. //) are
-   * stripped out.  For block comments, leading whitespace and an asterisk
-   * will be stripped from the beginning of each line other than the first.
-   * Newlines are included in the output.
-   * 
-   * Examples:
-   * 
-   *   optional int32 foo = 1;  // Comment attached to foo.
-   *   // Comment attached to bar.
-   *   optional int32 bar = 2;
-   * 
-   *   optional string baz = 3;
-   *   // Comment attached to baz.
-   *   // Another line attached to baz.
-   * 
-   *   // Comment attached to qux.
-   *   //
-   *   // Another line attached to qux.
-   *   optional double qux = 4;
-   * 
-   *   // Detached comment for corge. This is not leading or trailing comments
-   *   // to qux or corge because there are blank lines separating it from
-   *   // both.
-   * 
-   *   // Detached comment for corge paragraph 2.
-   * 
-   *   optional string corge = 5;
-   *   /* Block comment attached
-   *    * to corge.  Leading asterisks
-   *    * will be removed. *\/
-   *   /* Block comment attached to
-   *    * grault. *\/
-   *   optional int32 grault = 6;
-   * 
-   *   // ignored detached comments.
-   */
-
   leading_comments: string;
   trailing_comments: string;
   leading_detached_comments: string[];
@@ -2021,10 +1416,6 @@ export interface GeneratedCodeInfo {
  */
 
 export interface GeneratedCodeInfoSDKType {
-  /**
-   * An Annotation connects some span of text in generated code to an element
-   * of its generating .proto file.
-   */
   annotation: GeneratedCodeInfo_AnnotationSDKType[];
 }
 export interface GeneratedCodeInfo_Annotation {
@@ -2051,26 +1442,9 @@ export interface GeneratedCodeInfo_Annotation {
   end: number;
 }
 export interface GeneratedCodeInfo_AnnotationSDKType {
-  /**
-   * Identifies the element in the original source .proto file. This field
-   * is formatted the same as SourceCodeInfo.Location.path.
-   */
   path: number[];
-  /** Identifies the filesystem path to the original source .proto. */
-
   source_file: string;
-  /**
-   * Identifies the starting offset in bytes in the generated code
-   * that relates to the identified object.
-   */
-
   begin: number;
-  /**
-   * Identifies the ending offset in bytes in the generated code that
-   * relates to the identified offset. The end offset should be one past
-   * the last relevant byte (so the length of the text = end - begin).
-   */
-
   end: number;
 }