[{"name":"Proto.Google.Protobuf","comment":" This file was automatically generated by\n\n  - [`protoc-gen-elm`](https://www.npmjs.com/package/protoc-gen-elm) 3.1.0\n  - `protoc` 4.22.2\n  - the following specification files: `google/protobuf/any.proto, google/protobuf/api.proto, google/protobuf/descriptor.proto, google/protobuf/duration.proto, google/protobuf/empty.proto, google/protobuf/field_mask.proto, google/protobuf/source_context.proto, google/protobuf/struct.proto, google/protobuf/timestamp.proto, google/protobuf/type.proto, google/protobuf/wrappers.proto`\n\nTo run it, add a dependency via `elm install` on [`elm-protocol-buffers`](https://package.elm-lang.org/packages/eriktim/elm-protocol-buffers/1.2.0) version latest or higher.\n\nProtocol Buffers - Google's data interchange format\nCopyright 2008 Google Inc. All rights reserved.\n<https://developers.google.com/protocol-buffers/>\n\nRedistribution and use in source and binary forms, with or without\nmodification, are permitted provided that the following conditions are\nmet:\n\n     * Redistributions of source code must retain the above copyright\n\nnotice, this list of conditions and the following disclaimer.\n\\* Redistributions in binary form must reproduce the above\ncopyright notice, this list of conditions and the following disclaimer\nin the documentation and/or other materials provided with the\ndistribution.\n\\* Neither the name of Google Inc. nor the names of its\ncontributors may be used to endorse or promote products derived from\nthis software without specific prior written permission.\n\nTHIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS\n\"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT\nLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR\nA PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT\nOWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,\nSPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT\nLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,\nDATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY\nTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT\n(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE\nOF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.\n\nAuthor: kenton@google.com (Kenton Varda)\nBased on original Protocol Buffers design by\nSanjay Ghemawat, Jeff Dean, and others.\n\nThe messages in this file describe the definitions found in .proto files.\nA valid .proto file can be translated directly to a FileDescriptorProto\nwithout any other information (e.g. without reading its imports).\n\nProtocol Buffers - Google's data interchange format\nCopyright 2008 Google Inc. All rights reserved.\n<https://developers.google.com/protocol-buffers/>\n\nRedistribution and use in source and binary forms, with or without\nmodification, are permitted provided that the following conditions are\nmet:\n\n     * Redistributions of source code must retain the above copyright\n\nnotice, this list of conditions and the following disclaimer.\n\\* Redistributions in binary form must reproduce the above\ncopyright notice, this list of conditions and the following disclaimer\nin the documentation and/or other materials provided with the\ndistribution.\n\\* Neither the name of Google Inc. nor the names of its\ncontributors may be used to endorse or promote products derived from\nthis software without specific prior written permission.\n\nTHIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS\n\"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT\nLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR\nA PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT\nOWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,\nSPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT\nLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,\nDATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY\nTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT\n(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE\nOF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.\n\nWrappers for primitive (non-message) types. These types are useful\nfor embedding primitives in the `google.protobuf.Any` type and for places\nwhere we need to distinguish between the absence of a primitive\ntyped field and its default value.\n\nThese wrappers have no meaningful use within repeated fields as they lack\nthe ability to detect presence on individual elements.\nThese wrappers have no meaningful use within a map or a oneof since\nindividual entries of a map or fields of a oneof can already detect presence.\n\n@docs Any, Api, BoolValue, BytesValue, DescriptorProto, DescriptorProto_, DoubleValue, Duration, Empty, Enum, EnumDescriptorProto, EnumOptions\n@docs EnumValue, EnumValueDescriptorProto, EnumValueOptions, ExtensionRangeOptions, Field, FieldDescriptorProto, FieldMask, FieldOptions\n@docs FileDescriptorProto, FileDescriptorSet, FileOptions, FloatValue, GeneratedCodeInfo, Int32Value, Int64Value, ListValue, MessageOptions\n@docs Method, MethodDescriptorProto, MethodOptions, Mixin, NullValue, OneofDescriptorProto, OneofOptions, Option, ServiceDescriptorProto\n@docs ServiceOptions, SourceCodeInfo, SourceContext, StringValue, Struct, Syntax, Timestamp, Type, UInt32Value, UInt64Value, UninterpretedOption\n@docs Value, decodeAny, decodeApi, decodeBoolValue, decodeBytesValue, decodeDescriptorProto, decodeDoubleValue, decodeDuration, decodeEmpty\n@docs decodeEnum, decodeEnumDescriptorProto, decodeEnumOptions, decodeEnumValue, decodeEnumValueDescriptorProto, decodeEnumValueOptions\n@docs decodeExtensionRangeOptions, decodeField, decodeFieldDescriptorProto, decodeFieldMask, decodeFieldOptions\n@docs decodeFileDescriptorProto, decodeFileDescriptorSet, decodeFileOptions, decodeFloatValue, decodeGeneratedCodeInfo, decodeInt32Value\n@docs decodeInt64Value, decodeListValue, decodeMessageOptions, decodeMethod, decodeMethodDescriptorProto, decodeMethodOptions, decodeMixin\n@docs decodeNullValue, decodeOneofDescriptorProto, decodeOneofOptions, decodeOption, decodeServiceDescriptorProto, decodeServiceOptions\n@docs decodeSourceCodeInfo, decodeSourceContext, decodeStringValue, decodeStruct, decodeSyntax, decodeTimestamp, decodeType\n@docs decodeUInt32Value, decodeUInt64Value, decodeUninterpretedOption, decodeValue, defaultAny, defaultApi, defaultBoolValue\n@docs defaultBytesValue, defaultDescriptorProto, defaultDoubleValue, defaultDuration, defaultEmpty, defaultEnum\n@docs defaultEnumDescriptorProto, defaultEnumOptions, defaultEnumValue, defaultEnumValueDescriptorProto, defaultEnumValueOptions\n@docs defaultExtensionRangeOptions, defaultField, defaultFieldDescriptorProto, defaultFieldMask, defaultFieldOptions\n@docs defaultFileDescriptorProto, defaultFileDescriptorSet, defaultFileOptions, defaultFloatValue, defaultGeneratedCodeInfo\n@docs defaultInt32Value, defaultInt64Value, defaultListValue, defaultMessageOptions, defaultMethod, defaultMethodDescriptorProto\n@docs defaultMethodOptions, defaultMixin, defaultNullValue, defaultOneofDescriptorProto, defaultOneofOptions, defaultOption\n@docs defaultServiceDescriptorProto, defaultServiceOptions, defaultSourceCodeInfo, defaultSourceContext, defaultStringValue\n@docs defaultStruct, defaultSyntax, defaultTimestamp, defaultType, defaultUInt32Value, defaultUInt64Value, defaultUninterpretedOption\n@docs defaultValue, encodeAny, encodeApi, encodeBoolValue, encodeBytesValue, encodeDescriptorProto, encodeDoubleValue, encodeDuration\n@docs encodeEmpty, encodeEnum, encodeEnumDescriptorProto, encodeEnumOptions, encodeEnumValue, encodeEnumValueDescriptorProto\n@docs encodeEnumValueOptions, encodeExtensionRangeOptions, encodeField, encodeFieldDescriptorProto, encodeFieldMask, encodeFieldOptions\n@docs encodeFileDescriptorProto, encodeFileDescriptorSet, encodeFileOptions, encodeFloatValue, encodeGeneratedCodeInfo, encodeInt32Value\n@docs encodeInt64Value, encodeListValue, encodeMessageOptions, encodeMethod, encodeMethodDescriptorProto, encodeMethodOptions, encodeMixin\n@docs encodeNullValue, encodeOneofDescriptorProto, encodeOneofOptions, encodeOption, encodeServiceDescriptorProto, encodeServiceOptions\n@docs encodeSourceCodeInfo, encodeSourceContext, encodeStringValue, encodeStruct, encodeSyntax, encodeTimestamp, encodeType\n@docs encodeUInt32Value, encodeUInt64Value, encodeUninterpretedOption, encodeValue, fieldNumbersAny, fieldNumbersApi\n@docs fieldNumbersBoolValue, fieldNumbersBytesValue, fieldNumbersDescriptorProto, fieldNumbersDoubleValue, fieldNumbersDuration\n@docs fieldNumbersEmpty, fieldNumbersEnum, fieldNumbersEnumDescriptorProto, fieldNumbersEnumOptions, fieldNumbersEnumValue\n@docs fieldNumbersEnumValueDescriptorProto, fieldNumbersEnumValueOptions, fieldNumbersExtensionRangeOptions, fieldNumbersField\n@docs fieldNumbersFieldDescriptorProto, fieldNumbersFieldMask, fieldNumbersFieldOptions, fieldNumbersFileDescriptorProto\n@docs fieldNumbersFileDescriptorSet, fieldNumbersFileOptions, fieldNumbersFloatValue, fieldNumbersGeneratedCodeInfo\n@docs fieldNumbersInt32Value, fieldNumbersInt64Value, fieldNumbersListValue, fieldNumbersMessageOptions, fieldNumbersMethod\n@docs fieldNumbersMethodDescriptorProto, fieldNumbersMethodOptions, fieldNumbersMixin, fieldNumbersNullValue\n@docs fieldNumbersOneofDescriptorProto, fieldNumbersOneofOptions, fieldNumbersOption, fieldNumbersServiceDescriptorProto\n@docs fieldNumbersServiceOptions, fieldNumbersSourceCodeInfo, fieldNumbersSourceContext, fieldNumbersStringValue, fieldNumbersStruct\n@docs fieldNumbersSyntax, fieldNumbersTimestamp, fieldNumbersType, fieldNumbersUInt32Value, fieldNumbersUInt64Value\n@docs fieldNumbersUninterpretedOption, fieldNumbersValue, fromInternalNullValue, fromInternalSyntax, toInternalNullValue\n@docs toInternalSyntax, unwrapDescriptorProto, wrapDescriptorProto\n\n","unions":[{"name":"NullValue","comment":" `NullValue` is a singleton enumeration to represent the null value for the\n`Value` type union.\n\nThe JSON representation for `NullValue` is JSON `null`.\n\n","args":[],"cases":[["NULLVALUE",[]],["NullValueUnrecognized_",["Basics.Int"]]]},{"name":"Syntax","comment":" The syntax in which a protocol buffer element is defined.\n","args":[],"cases":[["SYNTAXPROTO2",[]],["SYNTAXPROTO3",[]],["SyntaxUnrecognized_",["Basics.Int"]]]}],"aliases":[{"name":"Any","comment":" `Any` contains an arbitrary serialized protocol buffer message along with a\nURL that describes the type of the serialized message.\n\nProtobuf library provides support to pack/unpack Any values in the form\nof utility functions or additional generated methods of the Any type.\n\nExample 1: Pack and unpack a message in C++.\n\n     Foo foo = ...;\n     Any any;\n     any.PackFrom(foo);\n     ...\n     if (any.UnpackTo(&foo)) {\n       ...\n     }\n\nExample 2: Pack and unpack a message in Java.\n\n     Foo foo = ...;\n     Any any = Any.pack(foo);\n     ...\n     if (any.is(Foo.class)) {\n       foo = any.unpack(Foo.class);\n     }\n     // or ...\n     if (any.isSameTypeAs(Foo.getDefaultInstance())) {\n       foo = any.unpack(Foo.getDefaultInstance());\n     }\n\nExample 3: Pack and unpack a message in Python.\n\n     foo = Foo(...)\n     any = Any()\n     any.Pack(foo)\n     ...\n     if any.Is(Foo.DESCRIPTOR):\n       any.Unpack(foo)\n       ...\n\nExample 4: Pack and unpack a message in Go\n\n      foo := &pb.Foo{...}\n      any, err := anypb.New(foo)\n      if err != nil {\n        ...\n      }\n      ...\n      foo := &pb.Foo{}\n      if err := any.UnmarshalTo(foo); err != nil {\n        ...\n      }\n\nThe pack methods provided by protobuf library will by default use\n'type.googleapis.com/full.type.name' as the type URL and the unpack\nmethods only use the fully qualified type name after the last '/'\nin the type URL, for example \"foo.bar.com/x/y.z\" will yield type\nname \"y.z\".\n\nJSON\n\nThe JSON representation of an `Any` value uses the regular\nrepresentation of the deserialized, embedded message, with an\nadditional field `@type` which contains the type URL. Example:\n\n     package google.profile;\n     message Person {\n       string first_name = 1;\n       string last_name = 2;\n     }\n\n     {\n       \"@type\": \"type.googleapis.com/google.profile.Person\",\n       \"firstName\": <string>,\n       \"lastName\": <string>\n     }\n\nIf the embedded message type is well-known and has a custom JSON\nrepresentation, that representation will be embedded adding a field\n`value` which holds the custom JSON in addition to the `@type`\nfield. Example (for message [google.protobuf.Duration]):\n\n     {\n       \"@type\": \"type.googleapis.com/google.protobuf.Duration\",\n       \"value\": \"1.212s\"\n     }\n\n\n## Fields\n\n\n### type\\_url\n\nA URL/resource name that uniquely identifies the type of the serialized\nprotocol buffer message. This string must contain at least\none \"/\" character. The last segment of the URL's path must represent\nthe fully qualified name of the type (as in\n`path/google.protobuf.Duration`). The name should be in a canonical form\n(e.g., leading \".\" is not accepted).\n\nIn practice, teams usually precompile into the binary all types that they\nexpect it to use in the context of Any. However, for URLs which use the\nscheme `http`, `https`, or no scheme, one can optionally set up a type\nserver that maps type URLs to message definitions as follows:\n\n  - If no scheme is provided, `https` is assumed.\n  - An HTTP GET on the URL must yield a [google.protobuf.Type]\n    value in binary format, or produce an error.\n  - Applications are allowed to cache lookup results based on the\n    URL, or have them precompiled into a binary to avoid any\n    lookup. Therefore, binary compatibility needs to be preserved\n    on changes to types. (Use versioned type names to manage\n    breaking changes.)\n\nNote: this functionality is not currently available in the official\nprotobuf release, and it is not used for type URLs beginning with\ntype.googleapis.com.\n\nSchemes other than `http`, `https` (or the empty scheme) might be\nused with implementation specific semantics.\n\n\n### value\n\nMust be a valid serialized protocol buffer of the above specified type.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__Any"},{"name":"Api","comment":" Api is a light-weight descriptor for an API Interface.\n\nInterfaces are also described as \"protocol buffer services\" in some contexts,\nsuch as by the \"service\" keyword in a .proto file, but they are different\nfrom API Services, which represent a concrete implementation of an interface\nas opposed to simply a description of methods and bindings. They are also\nsometimes simply referred to as \"APIs\" in other contexts, such as the name of\nthis message itself. See <https://cloud.google.com/apis/design/glossary> for\ndetailed terminology.\n\n\n## Fields\n\n\n### name\n\nThe fully qualified name of this interface, including package name\nfollowed by the interface's simple name.\n\n\n### methods\n\nThe methods of this interface, in unspecified order.\n\n\n### options\n\nAny metadata attached to the interface.\n\n\n### version\n\nA version string for this interface. If specified, must have the form\n`major-version.minor-version`, as in `1.10`. If the minor version is\nomitted, it defaults to zero. If the entire version field is empty, the\nmajor version is derived from the package name, as outlined below. If the\nfield is not empty, the version in the package name will be verified to be\nconsistent with what is provided here.\n\nThe versioning schema uses [semantic\nversioning](http://semver.org) where the major version number\nindicates a breaking change and the minor version an additive,\nnon-breaking change. Both version numbers are signals to users\nwhat to expect from different versions, and should be carefully\nchosen based on the product plan.\n\nThe major version is also reflected in the package name of the\ninterface, which must end in `v<major-version>`, as in\n`google.feature.v1`. For major versions 0 and 1, the suffix can\nbe omitted. Zero major versions must only be used for\nexperimental, non-GA interfaces.\n\n\n### source\\_context\n\nSource context for the protocol buffer service represented by this\nmessage.\n\n\n### mixins\n\nIncluded interfaces. See [Mixin].\n\n\n### syntax\n\nThe source syntax of the service.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__Api"},{"name":"BoolValue","comment":" Wrapper message for `bool`.\n\nThe JSON representation for `BoolValue` is JSON `true` and `false`.\n\n\n## Fields\n\n\n### value\n\nThe bool value.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__BoolValue"},{"name":"BytesValue","comment":" Wrapper message for `bytes`.\n\nThe JSON representation for `BytesValue` is JSON string.\n\n\n## Fields\n\n\n### value\n\nThe bytes value.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__BytesValue"},{"name":"DescriptorProto","comment":" Describes a message type.\n\n\n## Fields\n\n\n### reserved\\_name\n\nReserved field names, which may not be used by fields in the same message.\nA given name may only be reserved once.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__DescriptorProto"},{"name":"DescriptorProto_","comment":" Type wrapper for alias type `DescriptorProto` to avoid unlimited recursion.\n\nFor a more in-depth explanation why we need this, read this: <https://github.com/elm/compiler/blob/master/hints/recursive-alias.md>.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__DescriptorProto_"},{"name":"DoubleValue","comment":" Wrapper message for `double`.\n\nThe JSON representation for `DoubleValue` is JSON number.\n\n\n## Fields\n\n\n### value\n\nThe double value.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__DoubleValue"},{"name":"Duration","comment":" A Duration represents a signed, fixed-length span of time represented\nas a count of seconds and fractions of seconds at nanosecond\nresolution. It is independent of any calendar and concepts like \"day\"\nor \"month\". It is related to Timestamp in that the difference between\ntwo Timestamp values is a Duration and it can be added or subtracted\nfrom a Timestamp. Range is approximately +-10,000 years.\n\n\n# Examples\n\nExample 1: Compute Duration from two Timestamps in pseudo code.\n\n     Timestamp start = ...;\n     Timestamp end = ...;\n     Duration duration = ...;\n\n     duration.seconds = end.seconds - start.seconds;\n     duration.nanos = end.nanos - start.nanos;\n\n     if (duration.seconds < 0 && duration.nanos > 0) {\n       duration.seconds += 1;\n       duration.nanos -= 1000000000;\n     } else if (duration.seconds > 0 && duration.nanos < 0) {\n       duration.seconds -= 1;\n       duration.nanos += 1000000000;\n     }\n\nExample 2: Compute Timestamp from Timestamp + Duration in pseudo code.\n\n     Timestamp start = ...;\n     Duration duration = ...;\n     Timestamp end = ...;\n\n     end.seconds = start.seconds + duration.seconds;\n     end.nanos = start.nanos + duration.nanos;\n\n     if (end.nanos < 0) {\n       end.seconds -= 1;\n       end.nanos += 1000000000;\n     } else if (end.nanos >= 1000000000) {\n       end.seconds += 1;\n       end.nanos -= 1000000000;\n     }\n\nExample 3: Compute Duration from datetime.timedelta in Python.\n\n     td = datetime.timedelta(days=3, minutes=10)\n     duration = Duration()\n     duration.FromTimedelta(td)\n\n\n# JSON Mapping\n\nIn JSON format, the Duration type is encoded as a string rather than an\nobject, where the string ends in the suffix \"s\" (indicating seconds) and\nis preceded by the number of seconds, with nanoseconds expressed as\nfractional seconds. For example, 3 seconds with 0 nanoseconds should be\nencoded in JSON format as \"3s\", while 3 seconds and 1 nanosecond should\nbe expressed in JSON format as \"3.000000001s\", and 3 seconds and 1\nmicrosecond should be expressed in JSON format as \"3.000001s\".\n\n\n## Fields\n\n\n### seconds\n\nSigned seconds of the span of time. Must be from -315,576,000,000\nto +315,576,000,000 inclusive. Note: these bounds are computed from:\n60 sec/min \\* 60 min/hr \\* 24 hr/day \\* 365.25 days/year \\* 10000 years\n\n\n### nanos\n\nSigned fractions of a second at nanosecond resolution of the span\nof time. Durations less than one second are represented with a 0\n`seconds` field and a positive or negative `nanos` field. For durations\nof one second or more, a non-zero value for the `nanos` field must be\nof the same sign as the `seconds` field. Must be from -999,999,999\nto +999,999,999 inclusive.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__Duration"},{"name":"Empty","comment":" A generic empty message that you can re-use to avoid defining duplicated\nempty messages in your APIs. A typical example is to use it as the request\nor the response type of an API method. For instance:\n\n     service Foo {\n       rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty);\n     }\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__Empty"},{"name":"Enum","comment":" Enum type definition.\n\n\n## Fields\n\n\n### name\n\nEnum type name.\n\n\n### enumvalue\n\nEnum value definitions.\n\n\n### options\n\nProtocol buffer options.\n\n\n### source\\_context\n\nThe source context.\n\n\n### syntax\n\nThe source syntax.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__Enum"},{"name":"EnumDescriptorProto","comment":" Describes an enum type.\n\n\n## Fields\n\n\n### reserved\\_range\n\nRange of reserved numeric values. Reserved numeric values may not be used\nby enum values in the same enum declaration. Reserved ranges may not\noverlap.\n\n\n### reserved\\_name\n\nReserved enum value names, which may not be reused. A given name may only\nbe reserved once.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__EnumDescriptorProto"},{"name":"EnumOptions","comment":"\n\n\n## Fields\n\n\n### allow\\_alias\n\nSet this option to true to allow mapping different tag names to the same\nvalue.\n\n\n### deprecated\n\nIs this enum deprecated?\nDepending on the target platform, this can emit Deprecated annotations\nfor the enum, or it will be completely ignored; in the very least, this\nis a formalization for deprecating enums.\n\n\n### deprecated\\_legacy\\_json\\_field\\_conflicts\n\nEnable the legacy handling of JSON field name conflicts. This lowercases\nand strips underscored from the fields before comparison in proto3 only.\nThe new behavior takes `json_name` into account and applies to proto2 as\nwell.\nTODO(b/261750190) Remove this legacy behavior once downstream teams have\nhad time to migrate.\n\n\n### uninterpreted\\_option\n\nThe parser stores options it doesn't recognize here. See above.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__EnumOptions"},{"name":"EnumValue","comment":" Enum value definition.\n\n\n## Fields\n\n\n### name\n\nEnum value name.\n\n\n### number\n\nEnum value number.\n\n\n### options\n\nProtocol buffer options.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__EnumValue"},{"name":"EnumValueDescriptorProto","comment":" Describes a value within an enum.\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__EnumValueDescriptorProto"},{"name":"EnumValueOptions","comment":"\n\n\n## Fields\n\n\n### deprecated\n\nIs this enum value deprecated?\nDepending on the target platform, this can emit Deprecated annotations\nfor the enum value, or it will be completely ignored; in the very least,\nthis is a formalization for deprecating enum values.\n\n\n### uninterpreted\\_option\n\nThe parser stores options it doesn't recognize here. See above.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__EnumValueOptions"},{"name":"ExtensionRangeOptions","comment":"\n\n\n## Fields\n\n\n### uninterpreted\\_option\n\nThe parser stores options it doesn't recognize here. See above.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__ExtensionRangeOptions"},{"name":"Field","comment":" A single field of a message type.\n\n\n## Fields\n\n\n### kind\n\nThe field type.\n\n\n### cardinality\n\nThe field cardinality.\n\n\n### number\n\nThe field number.\n\n\n### name\n\nThe field name.\n\n\n### type\\_url\n\nThe field type URL, without the scheme, for message or enumeration\ntypes. Example: `\"type.googleapis.com/google.protobuf.Timestamp\"`.\n\n\n### oneof\\_index\n\nThe index of the field type in `Type.oneofs`, for message or enumeration\ntypes. The first type has index 1; zero means the type is not in the list.\n\n\n### packed\n\nWhether to use alternative packed wire representation.\n\n\n### options\n\nThe protocol buffer options.\n\n\n### json\\_name\n\nThe field JSON name.\n\n\n### default\\_value\n\nThe string value of the default value of this field. Proto2 syntax only.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__Field"},{"name":"FieldDescriptorProto","comment":" Describes a field within a message.\n\n\n## Fields\n\n\n### type\n\nIf type\\_name is set, this need not be set. If both this and type\\_name\nare set, this must be one of TYPE\\_ENUM, TYPE\\_MESSAGE or TYPE\\_GROUP.\n\n\n### type\\_name\n\nFor message and enum types, this is the name of the type. If the name\nstarts with a '.', it is fully-qualified. Otherwise, C++-like scoping\nrules are used to find the type (i.e. first the nested types within this\nmessage are searched, then within the parent, on up to the root\nnamespace).\n\n\n### extendee\n\nFor extensions, this is the name of the type being extended. It is\nresolved in the same manner as type\\_name.\n\n\n### default\\_value\n\nFor numeric types, contains the original text representation of the value.\nFor booleans, \"true\" or \"false\".\nFor strings, contains the default text contents (not escaped in any way).\nFor bytes, contains the C escaped value. All bytes >= 128 are escaped.\n\n\n### oneof\\_index\n\nIf set, gives the index of a oneof in the containing type's oneof\\_decl\nlist. This field is a member of that oneof.\n\n\n### json\\_name\n\nJSON name of this field. The value is set by protocol compiler. If the\nuser has set a \"json\\_name\" option on this field, that option's value\nwill be used. Otherwise, it's deduced from the field's name by converting\nit to camelCase.\n\n\n### proto3\\_optional\n\nIf true, this is a proto3 \"optional\". When a proto3 field is optional, it\ntracks presence regardless of field type.\n\nWhen proto3\\_optional is true, this field must be belong to a oneof to\nsignal to old proto3 clients that presence is tracked for this field. This\noneof is known as a \"synthetic\" oneof, and this field must be its sole\nmember (each proto3 optional field gets its own synthetic oneof). Synthetic\noneofs exist in the descriptor only, and do not generate any API. Synthetic\noneofs must be ordered after all \"real\" oneofs.\n\nFor message fields, proto3\\_optional doesn't create any semantic change,\nsince non-repeated message fields always track presence. However it still\nindicates the semantic detail of whether the user wrote \"optional\" or not.\nThis can be useful for round-tripping the .proto file. For consistency we\ngive message fields a synthetic oneof also, even though it is not required\nto track presence. This is especially important because the parser can't\ntell if a field is a message or an enum, so it must always create a\nsynthetic oneof.\n\nProto2 optional fields do not set this flag, because they already indicate\noptional with `LABEL_OPTIONAL`.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__FieldDescriptorProto"},{"name":"FieldMask","comment":" `FieldMask` represents a set of symbolic field paths, for example:\n\n     paths: \"f.a\"\n     paths: \"f.b.d\"\n\nHere `f` represents a field in some root message, `a` and `b`\nfields in the message found in `f`, and `d` a field found in the\nmessage in `f.b`.\n\nField masks are used to specify a subset of fields that should be\nreturned by a get operation or modified by an update operation.\nField masks also have a custom JSON encoding (see below).\n\n\n# Field Masks in Projections\n\nWhen used in the context of a projection, a response message or\nsub-message is filtered by the API to only contain those fields as\nspecified in the mask. For example, if the mask in the previous\nexample is applied to a response message as follows:\n\n     f {\n       a : 22\n       b {\n         d : 1\n         x : 2\n       }\n       y : 13\n     }\n     z: 8\n\nThe result will not contain specific values for fields x,y and z\n(their value will be set to the default, and omitted in proto text\noutput):\n\n     f {\n       a : 22\n       b {\n         d : 1\n       }\n     }\n\nA repeated field is not allowed except at the last position of a\npaths string.\n\nIf a FieldMask object is not present in a get operation, the\noperation applies to all fields (as if a FieldMask of all fields\nhad been specified).\n\nNote that a field mask does not necessarily apply to the\ntop-level response message. In case of a REST get operation, the\nfield mask applies directly to the response, but in case of a REST\nlist operation, the mask instead applies to each individual message\nin the returned resource list. In case of a REST custom method,\nother definitions may be used. Where the mask applies will be\nclearly documented together with its declaration in the API. In\nany case, the effect on the returned resource/resources is required\nbehavior for APIs.\n\n\n# Field Masks in Update Operations\n\nA field mask in update operations specifies which fields of the\ntargeted resource are going to be updated. The API is required\nto only change the values of the fields as specified in the mask\nand leave the others untouched. If a resource is passed in to\ndescribe the updated values, the API ignores the values of all\nfields not covered by the mask.\n\nIf a repeated field is specified for an update operation, new values will\nbe appended to the existing repeated field in the target resource. Note that\na repeated field is only allowed in the last position of a `paths` string.\n\nIf a sub-message is specified in the last position of the field mask for an\nupdate operation, then new value will be merged into the existing sub-message\nin the target resource.\n\nFor example, given the target message:\n\n     f {\n       b {\n         d: 1\n         x: 2\n       }\n       c: [1]\n     }\n\nAnd an update message:\n\n     f {\n       b {\n         d: 10\n       }\n       c: [2]\n     }\n\nthen if the field mask is:\n\npaths: [\"f.b\", \"f.c\"]\n\nthen the result will be:\n\n     f {\n       b {\n         d: 10\n         x: 2\n       }\n       c: [1, 2]\n     }\n\nAn implementation may provide options to override this default behavior for\nrepeated and message fields.\n\nIn order to reset a field's value to the default, the field must\nbe in the mask and set to the default value in the provided resource.\nHence, in order to reset all fields of a resource, provide a default\ninstance of the resource and set all fields in the mask, or do\nnot provide a mask as described below.\n\nIf a field mask is not present on update, the operation applies to\nall fields (as if a field mask of all fields has been specified).\nNote that in the presence of schema evolution, this may mean that\nfields the client does not know and has therefore not filled into\nthe request will be reset to their default. If this is unwanted\nbehavior, a specific service may require a client to always specify\na field mask, producing an error if not.\n\nAs with get operations, the location of the resource which\ndescribes the updated values in the request message depends on the\noperation kind. In any case, the effect of the field mask is\nrequired to be honored by the API.\n\n\n## Considerations for HTTP REST\n\nThe HTTP kind of an update operation which uses a field mask must\nbe set to PATCH instead of PUT in order to satisfy HTTP semantics\n(PUT must only be used for full updates).\n\n\n# JSON Encoding of Field Masks\n\nIn JSON, a field mask is encoded as a single string where paths are\nseparated by a comma. Fields name in each path are converted\nto/from lower-camel naming conventions.\n\nAs an example, consider the following message declarations:\n\n     message Profile {\n       User user = 1;\n       Photo photo = 2;\n     }\n     message User {\n       string display_name = 1;\n       string address = 2;\n     }\n\nIn proto a field mask for `Profile` may look as such:\n\n     mask {\n       paths: \"user.display_name\"\n       paths: \"photo\"\n     }\n\nIn JSON, the same mask is represented as below:\n\n     {\n       mask: \"user.displayName,photo\"\n     }\n\n\n# Field Masks and Oneof Fields\n\nField masks treat fields in oneofs just as regular fields. Consider the\nfollowing message:\n\n     message SampleMessage {\n       oneof test_oneof {\n         string name = 4;\n         SubMessage sub_message = 9;\n       }\n     }\n\nThe field mask can be:\n\n     mask {\n       paths: \"name\"\n     }\n\nOr:\n\n     mask {\n       paths: \"sub_message\"\n     }\n\nNote that oneof type names (\"test\\_oneof\" in this case) cannot be used in\npaths.\n\n\n## Field Mask Verification\n\nThe implementation of any API method which has a FieldMask type field in the\nrequest should verify the included field paths, and return an\n`INVALID_ARGUMENT` error if any path is unmappable.\n\n\n## Fields\n\n\n### paths\n\nThe set of field mask paths.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__FieldMask"},{"name":"FieldOptions","comment":"\n\n\n## Fields\n\n\n### ctype\n\nThe ctype option instructs the C++ code generator to use a different\nrepresentation of the field than it normally would. See the specific\noptions below. This option is not yet implemented in the open source\nrelease -- sorry, we'll try to include it in a future version!\n\n\n### packed\n\nThe packed option can be enabled for repeated primitive fields to enable\na more efficient representation on the wire. Rather than repeatedly\nwriting the tag and type for each element, the entire array is encoded as\na single length-delimited blob. In proto3, only explicit setting it to\nfalse will avoid using packed encoding.\n\n\n### jstype\n\nThe jstype option determines the JavaScript type used for values of the\nfield. The option is permitted only for 64 bit integral and fixed types\n(int64, uint64, sint64, fixed64, sfixed64). A field with jstype JS\\_STRING\nis represented as JavaScript string, which avoids loss of precision that\ncan happen when a large value is converted to a floating point JavaScript.\nSpecifying JS\\_NUMBER for the jstype causes the generated JavaScript code to\nuse the JavaScript \"number\" type. The behavior of the default option\nJS\\_NORMAL is implementation dependent.\n\nThis option is an enum to permit additional types to be added, e.g.\ngoog.math.Integer.\n\n\n### lazy\n\nShould this field be parsed lazily? Lazy applies only to message-type\nfields. It means that when the outer message is initially parsed, the\ninner message's contents will not be parsed but instead stored in encoded\nform. The inner message will actually be parsed when it is first accessed.\n\nThis is only a hint. Implementations are free to choose whether to use\neager or lazy parsing regardless of the value of this option. However,\nsetting this option true suggests that the protocol author believes that\nusing lazy parsing on this field is worth the additional bookkeeping\noverhead typically needed to implement it.\n\nThis option does not affect the public interface of any generated code;\nall method signatures remain the same. Furthermore, thread-safety of the\ninterface is not affected by this option; const methods remain safe to\ncall from multiple threads concurrently, while non-const methods continue\nto require exclusive access.\n\nNote that implementations may choose not to check required fields within\na lazy sub-message. That is, calling IsInitialized() on the outer message\nmay return true even if the inner message has missing required fields.\nThis is necessary because otherwise the inner message would have to be\nparsed in order to perform the check, defeating the purpose of lazy\nparsing. An implementation which chooses not to check required fields\nmust be consistent about it. That is, for any particular sub-message, the\nimplementation must either _always_ check its required fields, or _never_\ncheck its required fields, regardless of whether or not the message has\nbeen parsed.\n\nAs of May 2022, lazy verifies the contents of the byte stream during\nparsing. An invalid byte stream will cause the overall parsing to fail.\n\n\n### unverified\\_lazy\n\nunverified\\_lazy does no correctness checks on the byte stream. This should\nonly be used where lazy with verification is prohibitive for performance\nreasons.\n\n\n### deprecated\n\nIs this field deprecated?\nDepending on the target platform, this can emit Deprecated annotations\nfor accessors, or it will be completely ignored; in the very least, this\nis a formalization for deprecating fields.\n\n\n### weak\n\nFor Google-internal migration only. Do not use.\n\n\n### debug\\_redact\n\nIndicate that the field value should not be printed out when using debug\nformats, e.g. when the field contains sensitive credentials.\n\n\n### uninterpreted\\_option\n\nThe parser stores options it doesn't recognize here. See above.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__FieldOptions"},{"name":"FileDescriptorProto","comment":" Describes a complete .proto file.\n\n\n## Fields\n\n\n### name\n\nfile name, relative to root of source tree\n\n\n### package\n\ne.g. \"foo\", \"foo.bar\", etc.\n\n\n### dependency\n\nNames of files imported by this file.\n\n\n### public\\_dependency\n\nIndexes of the public imported files in the dependency list above.\n\n\n### weak\\_dependency\n\nIndexes of the weak imported files in the dependency list.\nFor Google-internal migration only. Do not use.\n\n\n### message\\_type\n\nAll top-level definitions in this file.\n\n\n### source\\_code\\_info\n\nThis field contains optional information about the original source code.\nYou may safely remove this entire field without harming runtime\nfunctionality of the descriptors -- the information is needed only by\ndevelopment tools.\n\n\n### syntax\n\nThe syntax of the proto file.\nThe supported values are \"proto2\", \"proto3\", and \"editions\".\n\nIf `edition` is present, this value must be \"editions\".\n\n\n### edition\n\nThe edition of the proto file, which is an opaque string.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__FileDescriptorProto"},{"name":"FileDescriptorSet","comment":" The protocol compiler can output a FileDescriptorSet containing the .proto\nfiles it parses.\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__FileDescriptorSet"},{"name":"FileOptions","comment":" ===================================================================\nOptions\n\nEach of the definitions above may have \"options\" attached. These are\njust annotations which may cause code to be generated slightly differently\nor may contain hints for code that manipulates protocol messages.\n\nClients may define custom options as extensions of the _Options messages.\nThese extensions may not yet be known at parsing time, so the parser cannot\nstore the values in them. Instead it stores them in a field in the _Options\nmessage called uninterpreted\\_option. This field must have the same name\nacross all \\*Options messages. We then use this field to populate the\nextensions when we build a descriptor, at which point all protos have been\nparsed and so all extensions are known.\n\nExtension numbers for custom options may be chosen as follows:\n\n  - For options which will only be used within a single application or\n    organization, or for experimental options, use field numbers 50000\n    through 99999. It is up to you to ensure that you do not use the\n    same number for multiple options.\n  - For options which will be published and used publicly by multiple\n    independent entities, e-mail protobuf-global-extension-registry@google.com\n    to reserve extension numbers. Simply provide your project name (e.g.\n    Objective-C plugin) and your project website (if available) -- there's no\n    need to explain how you intend to use them. Usually you only need one\n    extension number. You can declare multiple options with only one extension\n    number by putting them in a sub-message. See the Custom Options section of\n    the docs for examples:\n    <https://developers.google.com/protocol-buffers/docs/proto#options>\n    If this turns out to be popular, a web service will be set up\n    to automatically assign option numbers.\n\n\n## Fields\n\n\n### java\\_package\n\nSets the Java package where classes generated from this .proto will be\nplaced. By default, the proto package is used, but this is often\ninappropriate because proto packages do not normally start with backwards\ndomain names.\n\n\n### java\\_outer\\_classname\n\nControls the name of the wrapper Java class generated for the .proto file.\nThat class will always contain the .proto file's getDescriptor() method as\nwell as any top-level extensions defined in the .proto file.\nIf java\\_multiple\\_files is disabled, then all the other classes from the\n.proto file will be nested inside the single wrapper outer class.\n\n\n### java\\_multiple\\_files\n\nIf enabled, then the Java code generator will generate a separate .java\nfile for each top-level message, enum, and service defined in the .proto\nfile. Thus, these types will _not_ be nested inside the wrapper class\nnamed by java\\_outer\\_classname. However, the wrapper class will still be\ngenerated to contain the file's getDescriptor() method as well as any\ntop-level extensions defined in the file.\n\n\n### java\\_generate\\_equals\\_and\\_hash\n\nThis option does nothing.\n\n\n### java\\_string\\_check\\_utf8\n\nIf set true, then the Java2 code generator will generate code that\nthrows an exception whenever an attempt is made to assign a non-UTF-8\nbyte sequence to a string field.\nMessage reflection will do the same.\nHowever, an extension field still accepts non-UTF-8 byte sequences.\nThis option has no effect on when used with the lite runtime.\n\n\n### go\\_package\n\nSets the Go package where structs generated from this .proto will be\nplaced. If omitted, the Go package will be derived from the following:\n\n  - The basename of the package import path, if provided.\n  - Otherwise, the package statement in the .proto file, if present.\n  - Otherwise, the basename of the .proto file, without extension.\n\n\n### cc\\_generic\\_services\n\nShould generic services be generated in each language? \"Generic\" services\nare not specific to any particular RPC system. They are generated by the\nmain code generators in each language (without additional plugins).\nGeneric services were the only kind of service generation supported by\nearly versions of google.protobuf.\n\nGeneric services are now considered deprecated in favor of using plugins\nthat generate code specific to your particular RPC system. Therefore,\nthese default to false. Old code which depends on generic services should\nexplicitly set them to true.\n\n\n### deprecated\n\nIs this file deprecated?\nDepending on the target platform, this can emit Deprecated annotations\nfor everything in the file, or it will be completely ignored; in the very\nleast, this is a formalization for deprecating files.\n\n\n### cc\\_enable\\_arenas\n\nEnables the use of arenas for the proto messages in this file. This applies\nonly to generated classes for C++.\n\n\n### objc\\_class\\_prefix\n\nSets the objective c class prefix which is prepended to all objective c\ngenerated classes from this .proto. There is no default.\n\n\n### csharp\\_namespace\n\nNamespace for generated classes; defaults to the package.\n\n\n### swift\\_prefix\n\nBy default Swift generators will take the proto package and CamelCase it\nreplacing '.' with underscore and use that to prefix the types/symbols\ndefined. When this options is provided, they will use this value instead\nto prefix the types/symbols defined.\n\n\n### php\\_class\\_prefix\n\nSets the php class prefix which is prepended to all php generated classes\nfrom this .proto. Default is empty.\n\n\n### php\\_namespace\n\nUse this option to change the namespace of php generated classes. Default\nis empty. When this option is empty, the package name will be used for\ndetermining the namespace.\n\n\n### php\\_metadata\\_namespace\n\nUse this option to change the namespace of php generated metadata classes.\nDefault is empty. When this option is empty, the proto file name will be\nused for determining the namespace.\n\n\n### ruby\\_package\n\nUse this option to change the package of ruby generated classes. Default\nis empty. When this option is not set, the package name will be used for\ndetermining the ruby package.\n\n\n### uninterpreted\\_option\n\nThe parser stores options it doesn't recognize here.\nSee the documentation for the \"Options\" section above.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__FileOptions"},{"name":"FloatValue","comment":" Wrapper message for `float`.\n\nThe JSON representation for `FloatValue` is JSON number.\n\n\n## Fields\n\n\n### value\n\nThe float value.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__FloatValue"},{"name":"GeneratedCodeInfo","comment":" Describes the relationship between generated code and its original source\nfile. A GeneratedCodeInfo message is associated with only one generated\nsource file, but may contain references to different source .proto files.\n\n\n## Fields\n\n\n### annotation\n\nAn Annotation connects some span of text in generated code to an element\nof its generating .proto file.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__GeneratedCodeInfo"},{"name":"Int32Value","comment":" Wrapper message for `int32`.\n\nThe JSON representation for `Int32Value` is JSON number.\n\n\n## Fields\n\n\n### value\n\nThe int32 value.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__Int32Value"},{"name":"Int64Value","comment":" Wrapper message for `int64`.\n\nThe JSON representation for `Int64Value` is JSON string.\n\n\n## Fields\n\n\n### value\n\nThe int64 value.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__Int64Value"},{"name":"ListValue","comment":" `ListValue` is a wrapper around a repeated field of values.\n\nThe JSON representation for `ListValue` is JSON array.\n\n\n## Fields\n\n\n### values\n\nRepeated field of dynamically typed values.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__ListValue"},{"name":"MessageOptions","comment":"\n\n\n## Fields\n\n\n### message\\_set\\_wire\\_format\n\nSet true to use the old proto1 MessageSet wire format for extensions.\nThis is provided for backwards-compatibility with the MessageSet wire\nformat. You should not use this for any other reason: It's less\nefficient, has fewer features, and is more complicated.\n\nThe message must be defined exactly as follows:\nmessage Foo {\noption message\\_set\\_wire\\_format = true;\nextensions 4 to max;\n}\nNote that the message cannot have any defined fields; MessageSets only\nhave extensions.\n\nAll extensions of your type must be singular messages; e.g. they cannot\nbe int32s, enums, or repeated messages.\n\nBecause this is an option, the above two restrictions are not enforced by\nthe protocol compiler.\n\n\n### no\\_standard\\_descriptor\\_accessor\n\nDisables the generation of the standard \"descriptor()\" accessor, which can\nconflict with a field of the same name. This is meant to make migration\nfrom proto1 easier; new code should avoid fields named \"descriptor\".\n\n\n### deprecated\n\nIs this message deprecated?\nDepending on the target platform, this can emit Deprecated annotations\nfor the message, or it will be completely ignored; in the very least,\nthis is a formalization for deprecating messages.\n\n\n### map\\_entry\n\nNOTE: Do not set the option in .proto files. Always use the maps syntax\ninstead. The option should only be implicitly set by the proto compiler\nparser.\n\nWhether the message is an automatically generated map entry type for the\nmaps field.\n\nFor maps fields:\nmap<KeyType, ValueType> map\\_field = 1;\nThe parsed descriptor looks like:\nmessage MapFieldEntry {\noption map\\_entry = true;\noptional KeyType key = 1;\noptional ValueType value = 2;\n}\nrepeated MapFieldEntry map\\_field = 1;\n\nImplementations may choose not to generate the map\\_entry=true message, but\nuse a native map in the target language to hold the keys and values.\nThe reflection APIs in such implementations still need to work as\nif the field is a repeated message field.\n\n\n### deprecated\\_legacy\\_json\\_field\\_conflicts\n\nEnable the legacy handling of JSON field name conflicts. This lowercases\nand strips underscored from the fields before comparison in proto3 only.\nThe new behavior takes `json_name` into account and applies to proto2 as\nwell.\n\nThis should only be used as a temporary measure against broken builds due\nto the change in behavior for JSON field name conflicts.\n\nTODO(b/261750190) This is legacy behavior we plan to remove once downstream\nteams have had time to migrate.\n\n\n### uninterpreted\\_option\n\nThe parser stores options it doesn't recognize here. See above.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__MessageOptions"},{"name":"Method","comment":" Method represents a method of an API interface.\n\n\n## Fields\n\n\n### name\n\nThe simple name of this method.\n\n\n### request\\_type\\_url\n\nA URL of the input message type.\n\n\n### request\\_streaming\n\nIf true, the request is streamed.\n\n\n### response\\_type\\_url\n\nThe URL of the output message type.\n\n\n### response\\_streaming\n\nIf true, the response is streamed.\n\n\n### options\n\nAny metadata attached to the method.\n\n\n### syntax\n\nThe source syntax of this method.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__Method"},{"name":"MethodDescriptorProto","comment":" Describes a method of a service.\n\n\n## Fields\n\n\n### input\\_type\n\nInput and output type names. These are resolved in the same way as\nFieldDescriptorProto.type\\_name, but must refer to a message type.\n\n\n### client\\_streaming\n\nIdentifies if client streams multiple client messages\n\n\n### server\\_streaming\n\nIdentifies if server streams multiple server messages\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__MethodDescriptorProto"},{"name":"MethodOptions","comment":"\n\n\n## Fields\n\n\n### deprecated\n\nNote: Field numbers 1 through 32 are reserved for Google's internal RPC\nframework. We apologize for hoarding these numbers to ourselves, but\nwe were already using them long before we decided to release Protocol\nBuffers.\n\nIs this method deprecated?\nDepending on the target platform, this can emit Deprecated annotations\nfor the method, or it will be completely ignored; in the very least,\nthis is a formalization for deprecating methods.\n\n\n### uninterpreted\\_option\n\nThe parser stores options it doesn't recognize here. See above.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__MethodOptions"},{"name":"Mixin","comment":" Declares an API Interface to be included in this interface. The including\ninterface must redeclare all the methods from the included interface, but\ndocumentation and options are inherited as follows:\n\n  - If after comment and whitespace stripping, the documentation\n    string of the redeclared method is empty, it will be inherited\n    from the original method.\n\n  - Each annotation belonging to the service config (http,\n    visibility) which is not set in the redeclared method will be\n    inherited.\n\n  - If an http annotation is inherited, the path pattern will be\n    modified as follows. Any version prefix will be replaced by the\n    version of the including interface plus the [root] path if\n    specified.\n\nExample of a simple mixin:\n\n     package google.acl.v1;\n     service AccessControl {\n       // Get the underlying ACL object.\n       rpc GetAcl(GetAclRequest) returns (Acl) {\n         option (google.api.http).get = \"/v1/{resource=**}:getAcl\";\n       }\n     }\n\n     package google.storage.v2;\n     service Storage {\n       rpc GetAcl(GetAclRequest) returns (Acl);\n\n       // Get a data record.\n       rpc GetData(GetDataRequest) returns (Data) {\n         option (google.api.http).get = \"/v2/{resource=**}\";\n       }\n     }\n\nExample of a mixin configuration:\n\n     apis:\n     - name: google.storage.v2.Storage\n       mixins:\n       - name: google.acl.v1.AccessControl\n\nThe mixin construct implies that all methods in `AccessControl` are\nalso declared with same name and request/response types in\n`Storage`. A documentation generator or annotation processor will\nsee the effective `Storage.GetAcl` method after inheriting\ndocumentation and annotations as follows:\n\n     service Storage {\n       // Get the underlying ACL object.\n       rpc GetAcl(GetAclRequest) returns (Acl) {\n         option (google.api.http).get = \"/v2/{resource=**}:getAcl\";\n       }\n       ...\n     }\n\nNote how the version in the path pattern changed from `v1` to `v2`.\n\nIf the `root` field in the mixin is specified, it should be a\nrelative path under which inherited HTTP paths are placed. Example:\n\n     apis:\n     - name: google.storage.v2.Storage\n       mixins:\n       - name: google.acl.v1.AccessControl\n         root: acls\n\nThis implies the following inherited HTTP annotation:\n\n     service Storage {\n       // Get the underlying ACL object.\n       rpc GetAcl(GetAclRequest) returns (Acl) {\n         option (google.api.http).get = \"/v2/acls/{resource=**}:getAcl\";\n       }\n       ...\n     }\n\n\n## Fields\n\n\n### name\n\nThe fully qualified name of the interface which is included.\n\n\n### root\n\nIf non-empty specifies a path under which inherited HTTP paths\nare rooted.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__Mixin"},{"name":"OneofDescriptorProto","comment":" Describes a oneof.\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__OneofDescriptorProto"},{"name":"OneofOptions","comment":"\n\n\n## Fields\n\n\n### uninterpreted\\_option\n\nThe parser stores options it doesn't recognize here. See above.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__OneofOptions"},{"name":"Option","comment":" A protocol buffer option, which can be attached to a message, field,\nenumeration, etc.\n\n\n## Fields\n\n\n### name\n\nThe option's name. For protobuf built-in options (options defined in\ndescriptor.proto), this is the short name. For example, `\"map_entry\"`.\nFor custom options, it should be the fully-qualified name. For example,\n`\"google.api.http\"`.\n\n\n### value\n\nThe option's value packed in an Any message. If the value is a primitive,\nthe corresponding wrapper type defined in google/protobuf/wrappers.proto\nshould be used. If the value is an enum, it should be stored as an int32\nvalue using the google.protobuf.Int32Value type.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__Option"},{"name":"ServiceDescriptorProto","comment":" Describes a service.\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__ServiceDescriptorProto"},{"name":"ServiceOptions","comment":"\n\n\n## Fields\n\n\n### deprecated\n\nNote: Field numbers 1 through 32 are reserved for Google's internal RPC\nframework. We apologize for hoarding these numbers to ourselves, but\nwe were already using them long before we decided to release Protocol\nBuffers.\n\nIs this service deprecated?\nDepending on the target platform, this can emit Deprecated annotations\nfor the service, or it will be completely ignored; in the very least,\nthis is a formalization for deprecating services.\n\n\n### uninterpreted\\_option\n\nThe parser stores options it doesn't recognize here. See above.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__ServiceOptions"},{"name":"SourceCodeInfo","comment":" ===================================================================\nOptional source code info\n\nEncapsulates information about the original source file from which a\nFileDescriptorProto was generated.\n\n\n## Fields\n\n\n### location\n\nA Location identifies a piece of source code in a .proto file which\ncorresponds to a particular definition. This information is intended\nto be useful to IDEs, code indexers, documentation generators, and similar\ntools.\n\nFor example, say we have a file like:\nmessage Foo {\noptional string foo = 1;\n}\nLet's look at just the field definition:\noptional string foo = 1;\n^ ^^ ^^ ^ ^^^\na bc de f ghi\nWe have the following locations:\nspan path represents\n[a,i) [ 4, 0, 2, 0 ] The whole field definition.\n[a,b) [ 4, 0, 2, 0, 4 ] The label (optional).\n[c,d) [ 4, 0, 2, 0, 5 ] The type (string).\n[e,f) [ 4, 0, 2, 0, 1 ] The name (foo).\n[g,h) [ 4, 0, 2, 0, 3 ] The number (1).\n\nNotes:\n\n  - A location may refer to a repeated field itself (i.e. not to any\n    particular index within it). This is used whenever a set of elements are\n    logically enclosed in a single code segment. For example, an entire\n    extend block (possibly containing multiple extension definitions) will\n    have an outer location whose path refers to the \"extensions\" repeated\n    field without an index.\n  - Multiple locations may have the same path. This happens when a single\n    logical declaration is spread out across multiple places. The most\n    obvious example is the \"extend\" block again -- there may be multiple\n    extend blocks in the same scope, each of which will have the same path.\n  - A location's span is not always a subset of its parent's span. For\n    example, the \"extendee\" of an extension declaration appears at the\n    beginning of the \"extend\" block and is shared by all extensions within\n    the block.\n  - Just because a location's span is a subset of some other location's span\n    does not mean that it is a descendant. For example, a \"group\" defines\n    both a type and a field in a single declaration. Thus, the locations\n    corresponding to the type and field and their components will overlap.\n  - Code which tries to interpret locations should probably be designed to\n    ignore those that it doesn't understand, as more types of locations could\n    be recorded in the future.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__SourceCodeInfo"},{"name":"SourceContext","comment":" `SourceContext` represents information about the source of a\nprotobuf element, like the file in which it is defined.\n\n\n## Fields\n\n\n### file\\_name\n\nThe path-qualified name of the .proto file that contained the associated\nprotobuf element. For example: `\"google/protobuf/source_context.proto\"`.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__SourceContext"},{"name":"StringValue","comment":" Wrapper message for `string`.\n\nThe JSON representation for `StringValue` is JSON string.\n\n\n## Fields\n\n\n### value\n\nThe string value.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__StringValue"},{"name":"Struct","comment":" `Struct` represents a structured data value, consisting of fields\nwhich map to dynamically typed values. In some languages, `Struct`\nmight be supported by a native representation. For example, in\nscripting languages like JS a struct is represented as an\nobject. The details of that representation are described together\nwith the proto support for the language.\n\nThe JSON representation for `Struct` is JSON object.\n\n\n## Fields\n\n\n### fields\n\nUnordered map of dynamically typed values.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__Struct"},{"name":"Timestamp","comment":" A Timestamp represents a point in time independent of any time zone or local\ncalendar, encoded as a count of seconds and fractions of seconds at\nnanosecond resolution. The count is relative to an epoch at UTC midnight on\nJanuary 1, 1970, in the proleptic Gregorian calendar which extends the\nGregorian calendar backwards to year one.\n\nAll minutes are 60 seconds long. Leap seconds are \"smeared\" so that no leap\nsecond table is needed for interpretation, using a [24-hour linear\nsmear](https://developers.google.com/time/smear).\n\nThe range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By\nrestricting to that range, we ensure that we can convert to and from [RFC\n3339](https://www.ietf.org/rfc/rfc3339.txt) date strings.\n\n\n# Examples\n\nExample 1: Compute Timestamp from POSIX `time()`.\n\n     Timestamp timestamp;\n     timestamp.set_seconds(time(NULL));\n     timestamp.set_nanos(0);\n\nExample 2: Compute Timestamp from POSIX `gettimeofday()`.\n\n     struct timeval tv;\n     gettimeofday(&tv, NULL);\n\n     Timestamp timestamp;\n     timestamp.set_seconds(tv.tv_sec);\n     timestamp.set_nanos(tv.tv_usec * 1000);\n\nExample 3: Compute Timestamp from Win32 `GetSystemTimeAsFileTime()`.\n\n     FILETIME ft;\n     GetSystemTimeAsFileTime(&ft);\n     UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime;\n\n     // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z\n     // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z.\n     Timestamp timestamp;\n     timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL));\n     timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));\n\nExample 4: Compute Timestamp from Java `System.currentTimeMillis()`.\n\n     long millis = System.currentTimeMillis();\n\n     Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000)\n         .setNanos((int) ((millis % 1000) * 1000000)).build();\n\nExample 5: Compute Timestamp from Java `Instant.now()`.\n\n     Instant now = Instant.now();\n\n     Timestamp timestamp =\n         Timestamp.newBuilder().setSeconds(now.getEpochSecond())\n             .setNanos(now.getNano()).build();\n\nExample 6: Compute Timestamp from current time in Python.\n\n     timestamp = Timestamp()\n     timestamp.GetCurrentTime()\n\n\n# JSON Mapping\n\nIn JSON format, the Timestamp type is encoded as a string in the\n[RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the\nformat is \"{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac\\_sec}][.{frac_sec}]Z\"\nwhere {year} is always expressed using four digits while {month}, {day},\n{hour}, {min}, and {sec} are zero-padded to two digits each. The fractional\nseconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution),\nare optional. The \"Z\" suffix indicates the timezone (\"UTC\"); the timezone\nis required. A proto3 JSON serializer should always use UTC (as indicated by\n\"Z\") when printing the Timestamp type and a proto3 JSON parser should be\nable to accept both UTC and other timezones (as indicated by an offset).\n\nFor example, \"2017-01-15T01:30:15.01Z\" encodes 15.01 seconds past\n01:30 UTC on January 15, 2017.\n\nIn JavaScript, one can convert a Date object to this format using the\nstandard\n[toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString)\nmethod. In Python, a standard `datetime.datetime` object can be converted\nto this format using\n[`strftime`](https://docs.python.org/2/library/time.html#time.strftime) with\nthe time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use\nthe Joda Time's [`ISODateTimeFormat.dateTime()`](\n<http://www.joda.org/joda-time/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime%2D%2D>\n) to obtain a formatter capable of generating timestamps in this format.\n\n\n## Fields\n\n\n### seconds\n\nRepresents seconds of UTC time since Unix epoch\n1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to\n9999-12-31T23:59:59Z inclusive.\n\n\n### nanos\n\nNon-negative fractions of a second at nanosecond resolution. Negative\nsecond values with fractions must still have non-negative nanos values\nthat count forward in time. Must be from 0 to 999,999,999\ninclusive.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__Timestamp"},{"name":"Type","comment":" A protocol buffer message type.\n\n\n## Fields\n\n\n### name\n\nThe fully qualified message name.\n\n\n### fields\n\nThe list of fields.\n\n\n### oneofs\n\nThe list of types appearing in `oneof` definitions in this type.\n\n\n### options\n\nThe protocol buffer options.\n\n\n### source\\_context\n\nThe source context.\n\n\n### syntax\n\nThe source syntax.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__Type"},{"name":"UInt32Value","comment":" Wrapper message for `uint32`.\n\nThe JSON representation for `UInt32Value` is JSON number.\n\n\n## Fields\n\n\n### value\n\nThe uint32 value.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__UInt32Value"},{"name":"UInt64Value","comment":" Wrapper message for `uint64`.\n\nThe JSON representation for `UInt64Value` is JSON string.\n\n\n## Fields\n\n\n### value\n\nThe uint64 value.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__UInt64Value"},{"name":"UninterpretedOption","comment":" A message representing a option the parser does not recognize. This only\nappears in options protos created by the compiler::Parser class.\nDescriptorPool resolves these when building Descriptor objects. Therefore,\noptions protos in descriptor objects (e.g. returned by Descriptor::options(),\nor produced by Descriptor::CopyTo()) will never have UninterpretedOptions\nin them.\n\n\n## Fields\n\n\n### identifier\\_value\n\nThe value of the uninterpreted option, in whatever type the tokenizer\nidentified it as during parsing. Exactly one of these should be set.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__UninterpretedOption"},{"name":"Value","comment":" `Value` represents a dynamically typed value which can be either\nnull, a number, a string, a boolean, a recursive struct value, or a\nlist of values. A producer of value is expected to set one of these\nvariants. Absence of any variant indicates an error.\n\nThe JSON representation for `Value` is JSON value.\n\n","args":[],"type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__Value"}],"values":[{"name":"decodeAny","comment":" Declares how to decode a `Any` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.Any"},{"name":"decodeApi","comment":" Declares how to decode a `Api` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.Api"},{"name":"decodeBoolValue","comment":" Declares how to decode a `BoolValue` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.BoolValue"},{"name":"decodeBytesValue","comment":" Declares how to decode a `BytesValue` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.BytesValue"},{"name":"decodeDescriptorProto","comment":" Declares how to decode a `DescriptorProto` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.DescriptorProto"},{"name":"decodeDoubleValue","comment":" Declares how to decode a `DoubleValue` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.DoubleValue"},{"name":"decodeDuration","comment":" Declares how to decode a `Duration` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.Duration"},{"name":"decodeEmpty","comment":" Declares how to decode a `Empty` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.Empty"},{"name":"decodeEnum","comment":" Declares how to decode a `Enum` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.Enum"},{"name":"decodeEnumDescriptorProto","comment":" Declares how to decode a `EnumDescriptorProto` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.EnumDescriptorProto"},{"name":"decodeEnumOptions","comment":" Declares how to decode a `EnumOptions` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.EnumOptions"},{"name":"decodeEnumValue","comment":" Declares how to decode a `EnumValue` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.EnumValue"},{"name":"decodeEnumValueDescriptorProto","comment":" Declares how to decode a `EnumValueDescriptorProto` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.EnumValueDescriptorProto"},{"name":"decodeEnumValueOptions","comment":" Declares how to decode a `EnumValueOptions` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.EnumValueOptions"},{"name":"decodeExtensionRangeOptions","comment":" Declares how to decode a `ExtensionRangeOptions` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.ExtensionRangeOptions"},{"name":"decodeField","comment":" Declares how to decode a `Field` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.Field"},{"name":"decodeFieldDescriptorProto","comment":" Declares how to decode a `FieldDescriptorProto` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.FieldDescriptorProto"},{"name":"decodeFieldMask","comment":" Declares how to decode a `FieldMask` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.FieldMask"},{"name":"decodeFieldOptions","comment":" Declares how to decode a `FieldOptions` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.FieldOptions"},{"name":"decodeFileDescriptorProto","comment":" Declares how to decode a `FileDescriptorProto` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.FileDescriptorProto"},{"name":"decodeFileDescriptorSet","comment":" Declares how to decode a `FileDescriptorSet` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.FileDescriptorSet"},{"name":"decodeFileOptions","comment":" Declares how to decode a `FileOptions` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.FileOptions"},{"name":"decodeFloatValue","comment":" Declares how to decode a `FloatValue` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.FloatValue"},{"name":"decodeGeneratedCodeInfo","comment":" Declares how to decode a `GeneratedCodeInfo` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.GeneratedCodeInfo"},{"name":"decodeInt32Value","comment":" Declares how to decode a `Int32Value` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.Int32Value"},{"name":"decodeInt64Value","comment":" Declares how to decode a `Int64Value` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.Int64Value"},{"name":"decodeListValue","comment":" Declares how to decode a `ListValue` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.ListValue"},{"name":"decodeMessageOptions","comment":" Declares how to decode a `MessageOptions` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.MessageOptions"},{"name":"decodeMethod","comment":" Declares how to decode a `Method` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.Method"},{"name":"decodeMethodDescriptorProto","comment":" Declares how to decode a `MethodDescriptorProto` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.MethodDescriptorProto"},{"name":"decodeMethodOptions","comment":" Declares how to decode a `MethodOptions` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.MethodOptions"},{"name":"decodeMixin","comment":" Declares how to decode a `Mixin` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.Mixin"},{"name":"decodeNullValue","comment":" Declares how to decode a `NullValue` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.NullValue"},{"name":"decodeOneofDescriptorProto","comment":" Declares how to decode a `OneofDescriptorProto` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.OneofDescriptorProto"},{"name":"decodeOneofOptions","comment":" Declares how to decode a `OneofOptions` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.OneofOptions"},{"name":"decodeOption","comment":" Declares how to decode a `Option` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.Option"},{"name":"decodeServiceDescriptorProto","comment":" Declares how to decode a `ServiceDescriptorProto` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.ServiceDescriptorProto"},{"name":"decodeServiceOptions","comment":" Declares how to decode a `ServiceOptions` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.ServiceOptions"},{"name":"decodeSourceCodeInfo","comment":" Declares how to decode a `SourceCodeInfo` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.SourceCodeInfo"},{"name":"decodeSourceContext","comment":" Declares how to decode a `SourceContext` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.SourceContext"},{"name":"decodeStringValue","comment":" Declares how to decode a `StringValue` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.StringValue"},{"name":"decodeStruct","comment":" Declares how to decode a `Struct` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.Struct"},{"name":"decodeSyntax","comment":" Declares how to decode a `Syntax` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.Syntax"},{"name":"decodeTimestamp","comment":" Declares how to decode a `Timestamp` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.Timestamp"},{"name":"decodeType","comment":" Declares how to decode a `Type` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.Type"},{"name":"decodeUInt32Value","comment":" Declares how to decode a `UInt32Value` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.UInt32Value"},{"name":"decodeUInt64Value","comment":" Declares how to decode a `UInt64Value` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.UInt64Value"},{"name":"decodeUninterpretedOption","comment":" Declares how to decode a `UninterpretedOption` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.UninterpretedOption"},{"name":"decodeValue","comment":" Declares how to decode a `Value` from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.\n","type":"Protobuf.Decode.Decoder Proto.Google.Protobuf.Value"},{"name":"defaultAny","comment":" Default for Any. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.Any"},{"name":"defaultApi","comment":" Default for Api. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.Api"},{"name":"defaultBoolValue","comment":" Default for BoolValue. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.BoolValue"},{"name":"defaultBytesValue","comment":" Default for BytesValue. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.BytesValue"},{"name":"defaultDescriptorProto","comment":" Default for DescriptorProto. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.DescriptorProto"},{"name":"defaultDoubleValue","comment":" Default for DoubleValue. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.DoubleValue"},{"name":"defaultDuration","comment":" Default for Duration. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.Duration"},{"name":"defaultEmpty","comment":" Default for Empty. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.Empty"},{"name":"defaultEnum","comment":" Default for Enum. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.Enum"},{"name":"defaultEnumDescriptorProto","comment":" Default for EnumDescriptorProto. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.EnumDescriptorProto"},{"name":"defaultEnumOptions","comment":" Default for EnumOptions. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.EnumOptions"},{"name":"defaultEnumValue","comment":" Default for EnumValue. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.EnumValue"},{"name":"defaultEnumValueDescriptorProto","comment":" Default for EnumValueDescriptorProto. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.EnumValueDescriptorProto"},{"name":"defaultEnumValueOptions","comment":" Default for EnumValueOptions. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.EnumValueOptions"},{"name":"defaultExtensionRangeOptions","comment":" Default for ExtensionRangeOptions. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.ExtensionRangeOptions"},{"name":"defaultField","comment":" Default for Field. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.Field"},{"name":"defaultFieldDescriptorProto","comment":" Default for FieldDescriptorProto. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.FieldDescriptorProto"},{"name":"defaultFieldMask","comment":" Default for FieldMask. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.FieldMask"},{"name":"defaultFieldOptions","comment":" Default for FieldOptions. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.FieldOptions"},{"name":"defaultFileDescriptorProto","comment":" Default for FileDescriptorProto. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.FileDescriptorProto"},{"name":"defaultFileDescriptorSet","comment":" Default for FileDescriptorSet. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.FileDescriptorSet"},{"name":"defaultFileOptions","comment":" Default for FileOptions. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.FileOptions"},{"name":"defaultFloatValue","comment":" Default for FloatValue. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.FloatValue"},{"name":"defaultGeneratedCodeInfo","comment":" Default for GeneratedCodeInfo. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.GeneratedCodeInfo"},{"name":"defaultInt32Value","comment":" Default for Int32Value. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.Int32Value"},{"name":"defaultInt64Value","comment":" Default for Int64Value. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.Int64Value"},{"name":"defaultListValue","comment":" Default for ListValue. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.ListValue"},{"name":"defaultMessageOptions","comment":" Default for MessageOptions. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.MessageOptions"},{"name":"defaultMethod","comment":" Default for Method. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.Method"},{"name":"defaultMethodDescriptorProto","comment":" Default for MethodDescriptorProto. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.MethodDescriptorProto"},{"name":"defaultMethodOptions","comment":" Default for MethodOptions. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.MethodOptions"},{"name":"defaultMixin","comment":" Default for Mixin. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.Mixin"},{"name":"defaultNullValue","comment":" Default for NullValue. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.NullValue"},{"name":"defaultOneofDescriptorProto","comment":" Default for OneofDescriptorProto. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.OneofDescriptorProto"},{"name":"defaultOneofOptions","comment":" Default for OneofOptions. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.OneofOptions"},{"name":"defaultOption","comment":" Default for Option. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.Option"},{"name":"defaultServiceDescriptorProto","comment":" Default for ServiceDescriptorProto. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.ServiceDescriptorProto"},{"name":"defaultServiceOptions","comment":" Default for ServiceOptions. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.ServiceOptions"},{"name":"defaultSourceCodeInfo","comment":" Default for SourceCodeInfo. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.SourceCodeInfo"},{"name":"defaultSourceContext","comment":" Default for SourceContext. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.SourceContext"},{"name":"defaultStringValue","comment":" Default for StringValue. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.StringValue"},{"name":"defaultStruct","comment":" Default for Struct. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.Struct"},{"name":"defaultSyntax","comment":" Default for Syntax. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.Syntax"},{"name":"defaultTimestamp","comment":" Default for Timestamp. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.Timestamp"},{"name":"defaultType","comment":" Default for Type. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.Type"},{"name":"defaultUInt32Value","comment":" Default for UInt32Value. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.UInt32Value"},{"name":"defaultUInt64Value","comment":" Default for UInt64Value. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.UInt64Value"},{"name":"defaultUninterpretedOption","comment":" Default for UninterpretedOption. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.UninterpretedOption"},{"name":"defaultValue","comment":" Default for Value. Should only be used for 'required' decoders as an initial value.\n","type":"Proto.Google.Protobuf.Value"},{"name":"encodeAny","comment":" Declares how to encode a `Any` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.Any -> Protobuf.Encode.Encoder"},{"name":"encodeApi","comment":" Declares how to encode a `Api` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.Api -> Protobuf.Encode.Encoder"},{"name":"encodeBoolValue","comment":" Declares how to encode a `BoolValue` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.BoolValue -> Protobuf.Encode.Encoder"},{"name":"encodeBytesValue","comment":" Declares how to encode a `BytesValue` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.BytesValue -> Protobuf.Encode.Encoder"},{"name":"encodeDescriptorProto","comment":" Declares how to encode a `DescriptorProto` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.DescriptorProto -> Protobuf.Encode.Encoder"},{"name":"encodeDoubleValue","comment":" Declares how to encode a `DoubleValue` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.DoubleValue -> Protobuf.Encode.Encoder"},{"name":"encodeDuration","comment":" Declares how to encode a `Duration` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.Duration -> Protobuf.Encode.Encoder"},{"name":"encodeEmpty","comment":" Declares how to encode a `Empty` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.Empty -> Protobuf.Encode.Encoder"},{"name":"encodeEnum","comment":" Declares how to encode a `Enum` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.Enum -> Protobuf.Encode.Encoder"},{"name":"encodeEnumDescriptorProto","comment":" Declares how to encode a `EnumDescriptorProto` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.EnumDescriptorProto -> Protobuf.Encode.Encoder"},{"name":"encodeEnumOptions","comment":" Declares how to encode a `EnumOptions` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.EnumOptions -> Protobuf.Encode.Encoder"},{"name":"encodeEnumValue","comment":" Declares how to encode a `EnumValue` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.EnumValue -> Protobuf.Encode.Encoder"},{"name":"encodeEnumValueDescriptorProto","comment":" Declares how to encode a `EnumValueDescriptorProto` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.EnumValueDescriptorProto -> Protobuf.Encode.Encoder"},{"name":"encodeEnumValueOptions","comment":" Declares how to encode a `EnumValueOptions` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.EnumValueOptions -> Protobuf.Encode.Encoder"},{"name":"encodeExtensionRangeOptions","comment":" Declares how to encode a `ExtensionRangeOptions` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.ExtensionRangeOptions -> Protobuf.Encode.Encoder"},{"name":"encodeField","comment":" Declares how to encode a `Field` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.Field -> Protobuf.Encode.Encoder"},{"name":"encodeFieldDescriptorProto","comment":" Declares how to encode a `FieldDescriptorProto` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.FieldDescriptorProto -> Protobuf.Encode.Encoder"},{"name":"encodeFieldMask","comment":" Declares how to encode a `FieldMask` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.FieldMask -> Protobuf.Encode.Encoder"},{"name":"encodeFieldOptions","comment":" Declares how to encode a `FieldOptions` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.FieldOptions -> Protobuf.Encode.Encoder"},{"name":"encodeFileDescriptorProto","comment":" Declares how to encode a `FileDescriptorProto` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.FileDescriptorProto -> Protobuf.Encode.Encoder"},{"name":"encodeFileDescriptorSet","comment":" Declares how to encode a `FileDescriptorSet` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.FileDescriptorSet -> Protobuf.Encode.Encoder"},{"name":"encodeFileOptions","comment":" Declares how to encode a `FileOptions` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.FileOptions -> Protobuf.Encode.Encoder"},{"name":"encodeFloatValue","comment":" Declares how to encode a `FloatValue` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.FloatValue -> Protobuf.Encode.Encoder"},{"name":"encodeGeneratedCodeInfo","comment":" Declares how to encode a `GeneratedCodeInfo` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.GeneratedCodeInfo -> Protobuf.Encode.Encoder"},{"name":"encodeInt32Value","comment":" Declares how to encode a `Int32Value` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.Int32Value -> Protobuf.Encode.Encoder"},{"name":"encodeInt64Value","comment":" Declares how to encode a `Int64Value` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.Int64Value -> Protobuf.Encode.Encoder"},{"name":"encodeListValue","comment":" Declares how to encode a `ListValue` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.ListValue -> Protobuf.Encode.Encoder"},{"name":"encodeMessageOptions","comment":" Declares how to encode a `MessageOptions` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.MessageOptions -> Protobuf.Encode.Encoder"},{"name":"encodeMethod","comment":" Declares how to encode a `Method` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.Method -> Protobuf.Encode.Encoder"},{"name":"encodeMethodDescriptorProto","comment":" Declares how to encode a `MethodDescriptorProto` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.MethodDescriptorProto -> Protobuf.Encode.Encoder"},{"name":"encodeMethodOptions","comment":" Declares how to encode a `MethodOptions` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.MethodOptions -> Protobuf.Encode.Encoder"},{"name":"encodeMixin","comment":" Declares how to encode a `Mixin` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.Mixin -> Protobuf.Encode.Encoder"},{"name":"encodeNullValue","comment":" Declares how to encode a `NullValue` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.NullValue -> Protobuf.Encode.Encoder"},{"name":"encodeOneofDescriptorProto","comment":" Declares how to encode a `OneofDescriptorProto` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.OneofDescriptorProto -> Protobuf.Encode.Encoder"},{"name":"encodeOneofOptions","comment":" Declares how to encode a `OneofOptions` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.OneofOptions -> Protobuf.Encode.Encoder"},{"name":"encodeOption","comment":" Declares how to encode a `Option` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.Option -> Protobuf.Encode.Encoder"},{"name":"encodeServiceDescriptorProto","comment":" Declares how to encode a `ServiceDescriptorProto` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.ServiceDescriptorProto -> Protobuf.Encode.Encoder"},{"name":"encodeServiceOptions","comment":" Declares how to encode a `ServiceOptions` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.ServiceOptions -> Protobuf.Encode.Encoder"},{"name":"encodeSourceCodeInfo","comment":" Declares how to encode a `SourceCodeInfo` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.SourceCodeInfo -> Protobuf.Encode.Encoder"},{"name":"encodeSourceContext","comment":" Declares how to encode a `SourceContext` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.SourceContext -> Protobuf.Encode.Encoder"},{"name":"encodeStringValue","comment":" Declares how to encode a `StringValue` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.StringValue -> Protobuf.Encode.Encoder"},{"name":"encodeStruct","comment":" Declares how to encode a `Struct` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.Struct -> Protobuf.Encode.Encoder"},{"name":"encodeSyntax","comment":" Declares how to encode a `Syntax` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.Syntax -> Protobuf.Encode.Encoder"},{"name":"encodeTimestamp","comment":" Declares how to encode a `Timestamp` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.Timestamp -> Protobuf.Encode.Encoder"},{"name":"encodeType","comment":" Declares how to encode a `Type` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.Type -> Protobuf.Encode.Encoder"},{"name":"encodeUInt32Value","comment":" Declares how to encode a `UInt32Value` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.UInt32Value -> Protobuf.Encode.Encoder"},{"name":"encodeUInt64Value","comment":" Declares how to encode a `UInt64Value` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.UInt64Value -> Protobuf.Encode.Encoder"},{"name":"encodeUninterpretedOption","comment":" Declares how to encode a `UninterpretedOption` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.UninterpretedOption -> Protobuf.Encode.Encoder"},{"name":"encodeValue","comment":" Declares how to encode a `Value` to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.\n","type":"Proto.Google.Protobuf.Value -> Protobuf.Encode.Encoder"},{"name":"fieldNumbersAny","comment":" The field numbers for the fields of `Any`. This is mostly useful for internals, like documentation generation.\n","type":"{ typeUrl : Basics.Int, value : Basics.Int }"},{"name":"fieldNumbersApi","comment":" The field numbers for the fields of `Api`. This is mostly useful for internals, like documentation generation.\n","type":"{ name : Basics.Int, methods : Basics.Int, options : Basics.Int, version : Basics.Int, sourceContext : Basics.Int, mixins : Basics.Int, syntax : Basics.Int }"},{"name":"fieldNumbersBoolValue","comment":" The field numbers for the fields of `BoolValue`. This is mostly useful for internals, like documentation generation.\n","type":"{ value : Basics.Int }"},{"name":"fieldNumbersBytesValue","comment":" The field numbers for the fields of `BytesValue`. This is mostly useful for internals, like documentation generation.\n","type":"{ value : Basics.Int }"},{"name":"fieldNumbersDescriptorProto","comment":" The field numbers for the fields of `DescriptorProto`. This is mostly useful for internals, like documentation generation.\n","type":"{ name : Basics.Int, field : Basics.Int, extension : Basics.Int, nestedType : Basics.Int, enumType : Basics.Int, extensionRange : Basics.Int, oneofDecl : Basics.Int, options : Basics.Int, reservedRange : Basics.Int, reservedName : Basics.Int }"},{"name":"fieldNumbersDoubleValue","comment":" The field numbers for the fields of `DoubleValue`. This is mostly useful for internals, like documentation generation.\n","type":"{ value : Basics.Int }"},{"name":"fieldNumbersDuration","comment":" The field numbers for the fields of `Duration`. This is mostly useful for internals, like documentation generation.\n","type":"{ seconds : Basics.Int, nanos : Basics.Int }"},{"name":"fieldNumbersEmpty","comment":" The field numbers for the fields of `Empty`. This is mostly useful for internals, like documentation generation.\n","type":"{}"},{"name":"fieldNumbersEnum","comment":" The field numbers for the fields of `Enum`. This is mostly useful for internals, like documentation generation.\n","type":"{ name : Basics.Int, enumvalue : Basics.Int, options : Basics.Int, sourceContext : Basics.Int, syntax : Basics.Int }"},{"name":"fieldNumbersEnumDescriptorProto","comment":" The field numbers for the fields of `EnumDescriptorProto`. This is mostly useful for internals, like documentation generation.\n","type":"{ name : Basics.Int, value : Basics.Int, options : Basics.Int, reservedRange : Basics.Int, reservedName : Basics.Int }"},{"name":"fieldNumbersEnumOptions","comment":" The field numbers for the fields of `EnumOptions`. This is mostly useful for internals, like documentation generation.\n","type":"{ allowAlias : Basics.Int, deprecated : Basics.Int, deprecatedLegacyJsonFieldConflicts : Basics.Int, uninterpretedOption : Basics.Int }"},{"name":"fieldNumbersEnumValue","comment":" The field numbers for the fields of `EnumValue`. This is mostly useful for internals, like documentation generation.\n","type":"{ name : Basics.Int, number : Basics.Int, options : Basics.Int }"},{"name":"fieldNumbersEnumValueDescriptorProto","comment":" The field numbers for the fields of `EnumValueDescriptorProto`. This is mostly useful for internals, like documentation generation.\n","type":"{ name : Basics.Int, number : Basics.Int, options : Basics.Int }"},{"name":"fieldNumbersEnumValueOptions","comment":" The field numbers for the fields of `EnumValueOptions`. This is mostly useful for internals, like documentation generation.\n","type":"{ deprecated : Basics.Int, uninterpretedOption : Basics.Int }"},{"name":"fieldNumbersExtensionRangeOptions","comment":" The field numbers for the fields of `ExtensionRangeOptions`. This is mostly useful for internals, like documentation generation.\n","type":"{ uninterpretedOption : Basics.Int }"},{"name":"fieldNumbersField","comment":" The field numbers for the fields of `Field`. This is mostly useful for internals, like documentation generation.\n","type":"{ kind : Basics.Int, cardinality : Basics.Int, number : Basics.Int, name : Basics.Int, typeUrl : Basics.Int, oneofIndex : Basics.Int, packed : Basics.Int, options : Basics.Int, jsonName : Basics.Int, defaultValue : Basics.Int }"},{"name":"fieldNumbersFieldDescriptorProto","comment":" The field numbers for the fields of `FieldDescriptorProto`. This is mostly useful for internals, like documentation generation.\n","type":"{ name : Basics.Int, number : Basics.Int, label : Basics.Int, type_ : Basics.Int, typeName : Basics.Int, extendee : Basics.Int, defaultValue : Basics.Int, oneofIndex : Basics.Int, jsonName : Basics.Int, options : Basics.Int, proto3Optional : Basics.Int }"},{"name":"fieldNumbersFieldMask","comment":" The field numbers for the fields of `FieldMask`. This is mostly useful for internals, like documentation generation.\n","type":"{ paths : Basics.Int }"},{"name":"fieldNumbersFieldOptions","comment":" The field numbers for the fields of `FieldOptions`. This is mostly useful for internals, like documentation generation.\n","type":"{ ctype : Basics.Int, packed : Basics.Int, jstype : Basics.Int, lazy : Basics.Int, unverifiedLazy : Basics.Int, deprecated : Basics.Int, weak : Basics.Int, debugRedact : Basics.Int, retention : Basics.Int, target : Basics.Int, uninterpretedOption : Basics.Int }"},{"name":"fieldNumbersFileDescriptorProto","comment":" The field numbers for the fields of `FileDescriptorProto`. This is mostly useful for internals, like documentation generation.\n","type":"{ name : Basics.Int, package : Basics.Int, dependency : Basics.Int, publicDependency : Basics.Int, weakDependency : Basics.Int, messageType : Basics.Int, enumType : Basics.Int, service : Basics.Int, extension : Basics.Int, options : Basics.Int, sourceCodeInfo : Basics.Int, syntax : Basics.Int, edition : Basics.Int }"},{"name":"fieldNumbersFileDescriptorSet","comment":" The field numbers for the fields of `FileDescriptorSet`. This is mostly useful for internals, like documentation generation.\n","type":"{ file : Basics.Int }"},{"name":"fieldNumbersFileOptions","comment":" The field numbers for the fields of `FileOptions`. This is mostly useful for internals, like documentation generation.\n","type":"{ javaPackage : Basics.Int, javaOuterClassname : Basics.Int, javaMultipleFiles : Basics.Int, javaGenerateEqualsAndHash : Basics.Int, javaStringCheckUtf8 : Basics.Int, optimizeFor : Basics.Int, goPackage : Basics.Int, ccGenericServices : Basics.Int, javaGenericServices : Basics.Int, pyGenericServices : Basics.Int, phpGenericServices : Basics.Int, deprecated : Basics.Int, ccEnableArenas : Basics.Int, objcClassPrefix : Basics.Int, csharpNamespace : Basics.Int, swiftPrefix : Basics.Int, phpClassPrefix : Basics.Int, phpNamespace : Basics.Int, phpMetadataNamespace : Basics.Int, rubyPackage : Basics.Int, uninterpretedOption : Basics.Int }"},{"name":"fieldNumbersFloatValue","comment":" The field numbers for the fields of `FloatValue`. This is mostly useful for internals, like documentation generation.\n","type":"{ value : Basics.Int }"},{"name":"fieldNumbersGeneratedCodeInfo","comment":" The field numbers for the fields of `GeneratedCodeInfo`. This is mostly useful for internals, like documentation generation.\n","type":"{ annotation : Basics.Int }"},{"name":"fieldNumbersInt32Value","comment":" The field numbers for the fields of `Int32Value`. This is mostly useful for internals, like documentation generation.\n","type":"{ value : Basics.Int }"},{"name":"fieldNumbersInt64Value","comment":" The field numbers for the fields of `Int64Value`. This is mostly useful for internals, like documentation generation.\n","type":"{ value : Basics.Int }"},{"name":"fieldNumbersListValue","comment":" The field numbers for the fields of `ListValue`. This is mostly useful for internals, like documentation generation.\n","type":"{ values : Basics.Int }"},{"name":"fieldNumbersMessageOptions","comment":" The field numbers for the fields of `MessageOptions`. This is mostly useful for internals, like documentation generation.\n","type":"{ messageSetWireFormat : Basics.Int, noStandardDescriptorAccessor : Basics.Int, deprecated : Basics.Int, mapEntry : Basics.Int, deprecatedLegacyJsonFieldConflicts : Basics.Int, uninterpretedOption : Basics.Int }"},{"name":"fieldNumbersMethod","comment":" The field numbers for the fields of `Method`. This is mostly useful for internals, like documentation generation.\n","type":"{ name : Basics.Int, requestTypeUrl : Basics.Int, requestStreaming : Basics.Int, responseTypeUrl : Basics.Int, responseStreaming : Basics.Int, options : Basics.Int, syntax : Basics.Int }"},{"name":"fieldNumbersMethodDescriptorProto","comment":" The field numbers for the fields of `MethodDescriptorProto`. This is mostly useful for internals, like documentation generation.\n","type":"{ name : Basics.Int, inputType : Basics.Int, outputType : Basics.Int, options : Basics.Int, clientStreaming : Basics.Int, serverStreaming : Basics.Int }"},{"name":"fieldNumbersMethodOptions","comment":" The field numbers for the fields of `MethodOptions`. This is mostly useful for internals, like documentation generation.\n","type":"{ deprecated : Basics.Int, idempotencyLevel : Basics.Int, uninterpretedOption : Basics.Int }"},{"name":"fieldNumbersMixin","comment":" The field numbers for the fields of `Mixin`. This is mostly useful for internals, like documentation generation.\n","type":"{ name : Basics.Int, root : Basics.Int }"},{"name":"fieldNumbersNullValue","comment":" The field numbers for the fields of `NullValue`. This is mostly useful for internals, like documentation generation.\n","type":"Proto.Google.Protobuf.NullValue -> Basics.Int"},{"name":"fieldNumbersOneofDescriptorProto","comment":" The field numbers for the fields of `OneofDescriptorProto`. This is mostly useful for internals, like documentation generation.\n","type":"{ name : Basics.Int, options : Basics.Int }"},{"name":"fieldNumbersOneofOptions","comment":" The field numbers for the fields of `OneofOptions`. This is mostly useful for internals, like documentation generation.\n","type":"{ uninterpretedOption : Basics.Int }"},{"name":"fieldNumbersOption","comment":" The field numbers for the fields of `Option`. This is mostly useful for internals, like documentation generation.\n","type":"{ name : Basics.Int, value : Basics.Int }"},{"name":"fieldNumbersServiceDescriptorProto","comment":" The field numbers for the fields of `ServiceDescriptorProto`. This is mostly useful for internals, like documentation generation.\n","type":"{ name : Basics.Int, method : Basics.Int, options : Basics.Int }"},{"name":"fieldNumbersServiceOptions","comment":" The field numbers for the fields of `ServiceOptions`. This is mostly useful for internals, like documentation generation.\n","type":"{ deprecated : Basics.Int, uninterpretedOption : Basics.Int }"},{"name":"fieldNumbersSourceCodeInfo","comment":" The field numbers for the fields of `SourceCodeInfo`. This is mostly useful for internals, like documentation generation.\n","type":"{ location : Basics.Int }"},{"name":"fieldNumbersSourceContext","comment":" The field numbers for the fields of `SourceContext`. This is mostly useful for internals, like documentation generation.\n","type":"{ fileName : Basics.Int }"},{"name":"fieldNumbersStringValue","comment":" The field numbers for the fields of `StringValue`. This is mostly useful for internals, like documentation generation.\n","type":"{ value : Basics.Int }"},{"name":"fieldNumbersStruct","comment":" The field numbers for the fields of `Struct`. This is mostly useful for internals, like documentation generation.\n","type":"{ fields : Basics.Int }"},{"name":"fieldNumbersSyntax","comment":" The field numbers for the fields of `Syntax`. This is mostly useful for internals, like documentation generation.\n","type":"Proto.Google.Protobuf.Syntax -> Basics.Int"},{"name":"fieldNumbersTimestamp","comment":" The field numbers for the fields of `Timestamp`. This is mostly useful for internals, like documentation generation.\n","type":"{ seconds : Basics.Int, nanos : Basics.Int }"},{"name":"fieldNumbersType","comment":" The field numbers for the fields of `Type`. This is mostly useful for internals, like documentation generation.\n","type":"{ name : Basics.Int, fields : Basics.Int, oneofs : Basics.Int, options : Basics.Int, sourceContext : Basics.Int, syntax : Basics.Int }"},{"name":"fieldNumbersUInt32Value","comment":" The field numbers for the fields of `UInt32Value`. This is mostly useful for internals, like documentation generation.\n","type":"{ value : Basics.Int }"},{"name":"fieldNumbersUInt64Value","comment":" The field numbers for the fields of `UInt64Value`. This is mostly useful for internals, like documentation generation.\n","type":"{ value : Basics.Int }"},{"name":"fieldNumbersUninterpretedOption","comment":" The field numbers for the fields of `UninterpretedOption`. This is mostly useful for internals, like documentation generation.\n","type":"{ name : Basics.Int, identifierValue : Basics.Int, positiveIntValue : Basics.Int, negativeIntValue : Basics.Int, doubleValue : Basics.Int, stringValue : Basics.Int, aggregateValue : Basics.Int }"},{"name":"fieldNumbersValue","comment":" The field numbers for the fields of `Value`. This is mostly useful for internals, like documentation generation.\n","type":"{ kind : Proto.Google.Protobuf.Internals_.FieldNumbersProto__Google__Protobuf__Value__Kind__Kind }"},{"name":"fromInternalNullValue","comment":" Convert the internal type `Proto__Google__Protobuf__NullValue` into a `NullValue`.\n\nUsing two different types is necessary to avoid recursive module references while having readable constructor names.\n\n","type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__NullValue -> Proto.Google.Protobuf.NullValue"},{"name":"fromInternalSyntax","comment":" Convert the internal type `Proto__Google__Protobuf__Syntax` into a `Syntax`.\n\nUsing two different types is necessary to avoid recursive module references while having readable constructor names.\n\n","type":"Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__Syntax -> Proto.Google.Protobuf.Syntax"},{"name":"toInternalNullValue","comment":" Convert a `NullValue` into its internal representation `Proto__Google__Protobuf__NullValue`.\n\nUsing two different types is necessary to avoid recursive module references while having readable constructor names.\n\n","type":"Proto.Google.Protobuf.NullValue -> Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__NullValue"},{"name":"toInternalSyntax","comment":" Convert a `Syntax` into its internal representation `Proto__Google__Protobuf__Syntax`.\n\nUsing two different types is necessary to avoid recursive module references while having readable constructor names.\n\n","type":"Proto.Google.Protobuf.Syntax -> Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__Syntax"},{"name":"unwrapDescriptorProto","comment":" Unwrap a `DescriptorProto` from its wrapper `DescriptorProto_.`\n","type":"Proto.Google.Protobuf.DescriptorProto_ -> Proto.Google.Protobuf.DescriptorProto"},{"name":"wrapDescriptorProto","comment":" Wrap a `DescriptorProto` into its wrapper `DescriptorProto_.`\n","type":"Proto.Google.Protobuf.DescriptorProto -> Proto.Google.Protobuf.DescriptorProto_"}],"binops":[]}]