naijarea-ts 1.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,1338 @@
1
+ import { BinaryReader, BinaryWriter } from "@bufbuild/protobuf/wire";
2
+ export declare const protobufPackage = "google.protobuf";
3
+ /** The full set of known editions. */
4
+ export declare enum Edition {
5
+ /** EDITION_UNKNOWN - A placeholder for an unknown edition value. */
6
+ EDITION_UNKNOWN = 0,
7
+ /**
8
+ * EDITION_LEGACY - A placeholder edition for specifying default behaviors *before* a feature
9
+ * was first introduced. This is effectively an "infinite past".
10
+ */
11
+ EDITION_LEGACY = 900,
12
+ /**
13
+ * EDITION_PROTO2 - Legacy syntax "editions". These pre-date editions, but behave much like
14
+ * distinct editions. These can't be used to specify the edition of proto
15
+ * files, but feature definitions must supply proto2/proto3 defaults for
16
+ * backwards compatibility.
17
+ */
18
+ EDITION_PROTO2 = 998,
19
+ EDITION_PROTO3 = 999,
20
+ /**
21
+ * EDITION_2023 - Editions that have been released. The specific values are arbitrary and
22
+ * should not be depended on, but they will always be time-ordered for easy
23
+ * comparison.
24
+ */
25
+ EDITION_2023 = 1000,
26
+ EDITION_2024 = 1001,
27
+ /** EDITION_UNSTABLE - A placeholder edition for developing and testing unscheduled features. */
28
+ EDITION_UNSTABLE = 9999,
29
+ /**
30
+ * EDITION_1_TEST_ONLY - Placeholder editions for testing feature resolution. These should not be
31
+ * used or relied on outside of tests.
32
+ */
33
+ EDITION_1_TEST_ONLY = 1,
34
+ EDITION_2_TEST_ONLY = 2,
35
+ EDITION_99997_TEST_ONLY = 99997,
36
+ EDITION_99998_TEST_ONLY = 99998,
37
+ EDITION_99999_TEST_ONLY = 99999,
38
+ /**
39
+ * EDITION_MAX - Placeholder for specifying unbounded edition support. This should only
40
+ * ever be used by plugins that can expect to never require any changes to
41
+ * support a new edition.
42
+ */
43
+ EDITION_MAX = 2147483647,
44
+ UNRECOGNIZED = -1
45
+ }
46
+ export declare function editionFromJSON(object: any): Edition;
47
+ export declare function editionToJSON(object: Edition): string;
48
+ /**
49
+ * Describes the 'visibility' of a symbol with respect to the proto import
50
+ * system. Symbols can only be imported when the visibility rules do not prevent
51
+ * it (ex: local symbols cannot be imported). Visibility modifiers can only set
52
+ * on `message` and `enum` as they are the only types available to be referenced
53
+ * from other files.
54
+ */
55
+ export declare enum SymbolVisibility {
56
+ VISIBILITY_UNSET = 0,
57
+ VISIBILITY_LOCAL = 1,
58
+ VISIBILITY_EXPORT = 2,
59
+ UNRECOGNIZED = -1
60
+ }
61
+ export declare function symbolVisibilityFromJSON(object: any): SymbolVisibility;
62
+ export declare function symbolVisibilityToJSON(object: SymbolVisibility): string;
63
+ /**
64
+ * The protocol compiler can output a FileDescriptorSet containing the .proto
65
+ * files it parses.
66
+ */
67
+ export interface FileDescriptorSet {
68
+ file: FileDescriptorProto[];
69
+ }
70
+ /** Describes a complete .proto file. */
71
+ export interface FileDescriptorProto {
72
+ /** file name, relative to root of source tree */
73
+ name?: string | undefined;
74
+ /** e.g. "foo", "foo.bar", etc. */
75
+ package?: string | undefined;
76
+ /** Names of files imported by this file. */
77
+ dependency: string[];
78
+ /** Indexes of the public imported files in the dependency list above. */
79
+ publicDependency: number[];
80
+ /**
81
+ * Indexes of the weak imported files in the dependency list.
82
+ * For Google-internal migration only. Do not use.
83
+ */
84
+ weakDependency: number[];
85
+ /**
86
+ * Names of files imported by this file purely for the purpose of providing
87
+ * option extensions. These are excluded from the dependency list above.
88
+ */
89
+ optionDependency: string[];
90
+ /** All top-level definitions in this file. */
91
+ messageType: DescriptorProto[];
92
+ enumType: EnumDescriptorProto[];
93
+ service: ServiceDescriptorProto[];
94
+ extension: FieldDescriptorProto[];
95
+ options?: FileOptions | undefined;
96
+ /**
97
+ * This field contains optional information about the original source code.
98
+ * You may safely remove this entire field without harming runtime
99
+ * functionality of the descriptors -- the information is needed only by
100
+ * development tools.
101
+ */
102
+ sourceCodeInfo?: SourceCodeInfo | undefined;
103
+ /**
104
+ * The syntax of the proto file.
105
+ * The supported values are "proto2", "proto3", and "editions".
106
+ *
107
+ * If `edition` is present, this value must be "editions".
108
+ * WARNING: This field should only be used by protobuf plugins or special
109
+ * cases like the proto compiler. Other uses are discouraged and
110
+ * developers should rely on the protoreflect APIs for their client language.
111
+ */
112
+ syntax?: string | undefined;
113
+ /**
114
+ * The edition of the proto file.
115
+ * WARNING: This field should only be used by protobuf plugins or special
116
+ * cases like the proto compiler. Other uses are discouraged and
117
+ * developers should rely on the protoreflect APIs for their client language.
118
+ */
119
+ edition?: Edition | undefined;
120
+ }
121
+ /** Describes a message type. */
122
+ export interface DescriptorProto {
123
+ name?: string | undefined;
124
+ field: FieldDescriptorProto[];
125
+ extension: FieldDescriptorProto[];
126
+ nestedType: DescriptorProto[];
127
+ enumType: EnumDescriptorProto[];
128
+ extensionRange: DescriptorProto_ExtensionRange[];
129
+ oneofDecl: OneofDescriptorProto[];
130
+ options?: MessageOptions | undefined;
131
+ reservedRange: DescriptorProto_ReservedRange[];
132
+ /**
133
+ * Reserved field names, which may not be used by fields in the same message.
134
+ * A given name may only be reserved once.
135
+ */
136
+ reservedName: string[];
137
+ /** Support for `export` and `local` keywords on enums. */
138
+ visibility?: SymbolVisibility | undefined;
139
+ }
140
+ export interface DescriptorProto_ExtensionRange {
141
+ /** Inclusive. */
142
+ start?: number | undefined;
143
+ /** Exclusive. */
144
+ end?: number | undefined;
145
+ options?: ExtensionRangeOptions | undefined;
146
+ }
147
+ /**
148
+ * Range of reserved tag numbers. Reserved tag numbers may not be used by
149
+ * fields or extension ranges in the same message. Reserved ranges may
150
+ * not overlap.
151
+ */
152
+ export interface DescriptorProto_ReservedRange {
153
+ /** Inclusive. */
154
+ start?: number | undefined;
155
+ /** Exclusive. */
156
+ end?: number | undefined;
157
+ }
158
+ export interface ExtensionRangeOptions {
159
+ /** The parser stores options it doesn't recognize here. See above. */
160
+ uninterpretedOption: UninterpretedOption[];
161
+ /**
162
+ * For external users: DO NOT USE. We are in the process of open sourcing
163
+ * extension declaration and executing internal cleanups before it can be
164
+ * used externally.
165
+ */
166
+ declaration: ExtensionRangeOptions_Declaration[];
167
+ /** Any features defined in the specific edition. */
168
+ features?: FeatureSet | undefined;
169
+ /**
170
+ * The verification state of the range.
171
+ * TODO: flip the default to DECLARATION once all empty ranges
172
+ * are marked as UNVERIFIED.
173
+ */
174
+ verification?: ExtensionRangeOptions_VerificationState | undefined;
175
+ }
176
+ /** The verification state of the extension range. */
177
+ export declare enum ExtensionRangeOptions_VerificationState {
178
+ /** DECLARATION - All the extensions of the range must be declared. */
179
+ DECLARATION = 0,
180
+ UNVERIFIED = 1,
181
+ UNRECOGNIZED = -1
182
+ }
183
+ export declare function extensionRangeOptions_VerificationStateFromJSON(object: any): ExtensionRangeOptions_VerificationState;
184
+ export declare function extensionRangeOptions_VerificationStateToJSON(object: ExtensionRangeOptions_VerificationState): string;
185
+ export interface ExtensionRangeOptions_Declaration {
186
+ /** The extension number declared within the extension range. */
187
+ number?: number | undefined;
188
+ /**
189
+ * The fully-qualified name of the extension field. There must be a leading
190
+ * dot in front of the full name.
191
+ */
192
+ fullName?: string | undefined;
193
+ /**
194
+ * The fully-qualified type name of the extension field. Unlike
195
+ * Metadata.type, Declaration.type must have a leading dot for messages
196
+ * and enums.
197
+ */
198
+ type?: string | undefined;
199
+ /**
200
+ * If true, indicates that the number is reserved in the extension range,
201
+ * and any extension field with the number will fail to compile. Set this
202
+ * when a declared extension field is deleted.
203
+ */
204
+ reserved?: boolean | undefined;
205
+ /**
206
+ * If true, indicates that the extension must be defined as repeated.
207
+ * Otherwise the extension must be defined as optional.
208
+ */
209
+ repeated?: boolean | undefined;
210
+ }
211
+ /** Describes a field within a message. */
212
+ export interface FieldDescriptorProto {
213
+ name?: string | undefined;
214
+ number?: number | undefined;
215
+ label?: FieldDescriptorProto_Label | undefined;
216
+ /**
217
+ * If type_name is set, this need not be set. If both this and type_name
218
+ * are set, this must be one of TYPE_ENUM, TYPE_MESSAGE or TYPE_GROUP.
219
+ */
220
+ type?: FieldDescriptorProto_Type | undefined;
221
+ /**
222
+ * For message and enum types, this is the name of the type. If the name
223
+ * starts with a '.', it is fully-qualified. Otherwise, C++-like scoping
224
+ * rules are used to find the type (i.e. first the nested types within this
225
+ * message are searched, then within the parent, on up to the root
226
+ * namespace).
227
+ */
228
+ typeName?: string | undefined;
229
+ /**
230
+ * For extensions, this is the name of the type being extended. It is
231
+ * resolved in the same manner as type_name.
232
+ */
233
+ extendee?: string | undefined;
234
+ /**
235
+ * For numeric types, contains the original text representation of the value.
236
+ * For booleans, "true" or "false".
237
+ * For strings, contains the default text contents (not escaped in any way).
238
+ * For bytes, contains the C escaped value. All bytes >= 128 are escaped.
239
+ */
240
+ defaultValue?: string | undefined;
241
+ /**
242
+ * If set, gives the index of a oneof in the containing type's oneof_decl
243
+ * list. This field is a member of that oneof.
244
+ */
245
+ oneofIndex?: number | undefined;
246
+ /**
247
+ * JSON name of this field. The value is set by protocol compiler. If the
248
+ * user has set a "json_name" option on this field, that option's value
249
+ * will be used. Otherwise, it's deduced from the field's name by converting
250
+ * it to camelCase.
251
+ */
252
+ jsonName?: string | undefined;
253
+ options?: FieldOptions | undefined;
254
+ /**
255
+ * If true, this is a proto3 "optional". When a proto3 field is optional, it
256
+ * tracks presence regardless of field type.
257
+ *
258
+ * When proto3_optional is true, this field must belong to a oneof to signal
259
+ * to old proto3 clients that presence is tracked for this field. This oneof
260
+ * is known as a "synthetic" oneof, and this field must be its sole member
261
+ * (each proto3 optional field gets its own synthetic oneof). Synthetic oneofs
262
+ * exist in the descriptor only, and do not generate any API. Synthetic oneofs
263
+ * must be ordered after all "real" oneofs.
264
+ *
265
+ * For message fields, proto3_optional doesn't create any semantic change,
266
+ * since non-repeated message fields always track presence. However it still
267
+ * indicates the semantic detail of whether the user wrote "optional" or not.
268
+ * This can be useful for round-tripping the .proto file. For consistency we
269
+ * give message fields a synthetic oneof also, even though it is not required
270
+ * to track presence. This is especially important because the parser can't
271
+ * tell if a field is a message or an enum, so it must always create a
272
+ * synthetic oneof.
273
+ *
274
+ * Proto2 optional fields do not set this flag, because they already indicate
275
+ * optional with `LABEL_OPTIONAL`.
276
+ */
277
+ proto3Optional?: boolean | undefined;
278
+ }
279
+ export declare enum FieldDescriptorProto_Type {
280
+ /**
281
+ * TYPE_DOUBLE - 0 is reserved for errors.
282
+ * Order is weird for historical reasons.
283
+ */
284
+ TYPE_DOUBLE = 1,
285
+ TYPE_FLOAT = 2,
286
+ /**
287
+ * TYPE_INT64 - Not ZigZag encoded. Negative numbers take 10 bytes. Use TYPE_SINT64 if
288
+ * negative values are likely.
289
+ */
290
+ TYPE_INT64 = 3,
291
+ TYPE_UINT64 = 4,
292
+ /**
293
+ * TYPE_INT32 - Not ZigZag encoded. Negative numbers take 10 bytes. Use TYPE_SINT32 if
294
+ * negative values are likely.
295
+ */
296
+ TYPE_INT32 = 5,
297
+ TYPE_FIXED64 = 6,
298
+ TYPE_FIXED32 = 7,
299
+ TYPE_BOOL = 8,
300
+ TYPE_STRING = 9,
301
+ /**
302
+ * TYPE_GROUP - Tag-delimited aggregate.
303
+ * Group type is deprecated and not supported after google.protobuf. However, Proto3
304
+ * implementations should still be able to parse the group wire format and
305
+ * treat group fields as unknown fields. In Editions, the group wire format
306
+ * can be enabled via the `message_encoding` feature.
307
+ */
308
+ TYPE_GROUP = 10,
309
+ /** TYPE_MESSAGE - Length-delimited aggregate. */
310
+ TYPE_MESSAGE = 11,
311
+ /** TYPE_BYTES - New in version 2. */
312
+ TYPE_BYTES = 12,
313
+ TYPE_UINT32 = 13,
314
+ TYPE_ENUM = 14,
315
+ TYPE_SFIXED32 = 15,
316
+ TYPE_SFIXED64 = 16,
317
+ /** TYPE_SINT32 - Uses ZigZag encoding. */
318
+ TYPE_SINT32 = 17,
319
+ /** TYPE_SINT64 - Uses ZigZag encoding. */
320
+ TYPE_SINT64 = 18,
321
+ UNRECOGNIZED = -1
322
+ }
323
+ export declare function fieldDescriptorProto_TypeFromJSON(object: any): FieldDescriptorProto_Type;
324
+ export declare function fieldDescriptorProto_TypeToJSON(object: FieldDescriptorProto_Type): string;
325
+ export declare enum FieldDescriptorProto_Label {
326
+ /** LABEL_OPTIONAL - 0 is reserved for errors */
327
+ LABEL_OPTIONAL = 1,
328
+ LABEL_REPEATED = 3,
329
+ /**
330
+ * LABEL_REQUIRED - The required label is only allowed in google.protobuf. In proto3 and Editions
331
+ * it's explicitly prohibited. In Editions, the `field_presence` feature
332
+ * can be used to get this behavior.
333
+ */
334
+ LABEL_REQUIRED = 2,
335
+ UNRECOGNIZED = -1
336
+ }
337
+ export declare function fieldDescriptorProto_LabelFromJSON(object: any): FieldDescriptorProto_Label;
338
+ export declare function fieldDescriptorProto_LabelToJSON(object: FieldDescriptorProto_Label): string;
339
+ /** Describes a oneof. */
340
+ export interface OneofDescriptorProto {
341
+ name?: string | undefined;
342
+ options?: OneofOptions | undefined;
343
+ }
344
+ /** Describes an enum type. */
345
+ export interface EnumDescriptorProto {
346
+ name?: string | undefined;
347
+ value: EnumValueDescriptorProto[];
348
+ options?: EnumOptions | undefined;
349
+ /**
350
+ * Range of reserved numeric values. Reserved numeric values may not be used
351
+ * by enum values in the same enum declaration. Reserved ranges may not
352
+ * overlap.
353
+ */
354
+ reservedRange: EnumDescriptorProto_EnumReservedRange[];
355
+ /**
356
+ * Reserved enum value names, which may not be reused. A given name may only
357
+ * be reserved once.
358
+ */
359
+ reservedName: string[];
360
+ /** Support for `export` and `local` keywords on enums. */
361
+ visibility?: SymbolVisibility | undefined;
362
+ }
363
+ /**
364
+ * Range of reserved numeric values. Reserved values may not be used by
365
+ * entries in the same enum. Reserved ranges may not overlap.
366
+ *
367
+ * Note that this is distinct from DescriptorProto.ReservedRange in that it
368
+ * is inclusive such that it can appropriately represent the entire int32
369
+ * domain.
370
+ */
371
+ export interface EnumDescriptorProto_EnumReservedRange {
372
+ /** Inclusive. */
373
+ start?: number | undefined;
374
+ /** Inclusive. */
375
+ end?: number | undefined;
376
+ }
377
+ /** Describes a value within an enum. */
378
+ export interface EnumValueDescriptorProto {
379
+ name?: string | undefined;
380
+ number?: number | undefined;
381
+ options?: EnumValueOptions | undefined;
382
+ }
383
+ /** Describes a service. */
384
+ export interface ServiceDescriptorProto {
385
+ name?: string | undefined;
386
+ method: MethodDescriptorProto[];
387
+ options?: ServiceOptions | undefined;
388
+ }
389
+ /** Describes a method of a service. */
390
+ export interface MethodDescriptorProto {
391
+ name?: string | undefined;
392
+ /**
393
+ * Input and output type names. These are resolved in the same way as
394
+ * FieldDescriptorProto.type_name, but must refer to a message type.
395
+ */
396
+ inputType?: string | undefined;
397
+ outputType?: string | undefined;
398
+ options?: MethodOptions | undefined;
399
+ /** Identifies if client streams multiple client messages */
400
+ clientStreaming?: boolean | undefined;
401
+ /** Identifies if server streams multiple server messages */
402
+ serverStreaming?: boolean | undefined;
403
+ }
404
+ export interface FileOptions {
405
+ /**
406
+ * Sets the Java package where classes generated from this .proto will be
407
+ * placed. By default, the proto package is used, but this is often
408
+ * inappropriate because proto packages do not normally start with backwards
409
+ * domain names.
410
+ */
411
+ javaPackage?: string | undefined;
412
+ /**
413
+ * Controls the name of the wrapper Java class generated for the .proto file.
414
+ * That class will always contain the .proto file's getDescriptor() method as
415
+ * well as any top-level extensions defined in the .proto file.
416
+ * If java_multiple_files is disabled, then all the other classes from the
417
+ * .proto file will be nested inside the single wrapper outer class.
418
+ */
419
+ javaOuterClassname?: string | undefined;
420
+ /**
421
+ * If enabled, then the Java code generator will generate a separate .java
422
+ * file for each top-level message, enum, and service defined in the .proto
423
+ * file. Thus, these types will *not* be nested inside the wrapper class
424
+ * named by java_outer_classname. However, the wrapper class will still be
425
+ * generated to contain the file's getDescriptor() method as well as any
426
+ * top-level extensions defined in the file.
427
+ */
428
+ javaMultipleFiles?: boolean | undefined;
429
+ /**
430
+ * This option does nothing.
431
+ *
432
+ * @deprecated
433
+ */
434
+ javaGenerateEqualsAndHash?: boolean | undefined;
435
+ /**
436
+ * A proto2 file can set this to true to opt in to UTF-8 checking for Java,
437
+ * which will throw an exception if invalid UTF-8 is parsed from the wire or
438
+ * assigned to a string field.
439
+ *
440
+ * TODO: clarify exactly what kinds of field types this option
441
+ * applies to, and update these docs accordingly.
442
+ *
443
+ * Proto3 files already perform these checks. Setting the option explicitly to
444
+ * false has no effect: it cannot be used to opt proto3 files out of UTF-8
445
+ * checks.
446
+ */
447
+ javaStringCheckUtf8?: boolean | undefined;
448
+ optimizeFor?: FileOptions_OptimizeMode | undefined;
449
+ /**
450
+ * Sets the Go package where structs generated from this .proto will be
451
+ * placed. If omitted, the Go package will be derived from the following:
452
+ * - The basename of the package import path, if provided.
453
+ * - Otherwise, the package statement in the .proto file, if present.
454
+ * - Otherwise, the basename of the .proto file, without extension.
455
+ */
456
+ goPackage?: string | undefined;
457
+ /**
458
+ * Should generic services be generated in each language? "Generic" services
459
+ * are not specific to any particular RPC system. They are generated by the
460
+ * main code generators in each language (without additional plugins).
461
+ * Generic services were the only kind of service generation supported by
462
+ * early versions of google.protobuf.
463
+ *
464
+ * Generic services are now considered deprecated in favor of using plugins
465
+ * that generate code specific to your particular RPC system. Therefore,
466
+ * these default to false. Old code which depends on generic services should
467
+ * explicitly set them to true.
468
+ */
469
+ ccGenericServices?: boolean | undefined;
470
+ javaGenericServices?: boolean | undefined;
471
+ pyGenericServices?: boolean | undefined;
472
+ /**
473
+ * Is this file deprecated?
474
+ * Depending on the target platform, this can emit Deprecated annotations
475
+ * for everything in the file, or it will be completely ignored; in the very
476
+ * least, this is a formalization for deprecating files.
477
+ */
478
+ deprecated?: boolean | undefined;
479
+ /**
480
+ * Enables the use of arenas for the proto messages in this file. This applies
481
+ * only to generated classes for C++.
482
+ */
483
+ ccEnableArenas?: boolean | undefined;
484
+ /**
485
+ * Sets the objective c class prefix which is prepended to all objective c
486
+ * generated classes from this .proto. There is no default.
487
+ */
488
+ objcClassPrefix?: string | undefined;
489
+ /** Namespace for generated classes; defaults to the package. */
490
+ csharpNamespace?: string | undefined;
491
+ /**
492
+ * By default Swift generators will take the proto package and CamelCase it
493
+ * replacing '.' with underscore and use that to prefix the types/symbols
494
+ * defined. When this options is provided, they will use this value instead
495
+ * to prefix the types/symbols defined.
496
+ */
497
+ swiftPrefix?: string | undefined;
498
+ /**
499
+ * Sets the php class prefix which is prepended to all php generated classes
500
+ * from this .proto. Default is empty.
501
+ */
502
+ phpClassPrefix?: string | undefined;
503
+ /**
504
+ * Use this option to change the namespace of php generated classes. Default
505
+ * is empty. When this option is empty, the package name will be used for
506
+ * determining the namespace.
507
+ */
508
+ phpNamespace?: string | undefined;
509
+ /**
510
+ * Use this option to change the namespace of php generated metadata classes.
511
+ * Default is empty. When this option is empty, the proto file name will be
512
+ * used for determining the namespace.
513
+ */
514
+ phpMetadataNamespace?: string | undefined;
515
+ /**
516
+ * Use this option to change the package of ruby generated classes. Default
517
+ * is empty. When this option is not set, the package name will be used for
518
+ * determining the ruby package.
519
+ */
520
+ rubyPackage?: string | undefined;
521
+ /**
522
+ * Any features defined in the specific edition.
523
+ * WARNING: This field should only be used by protobuf plugins or special
524
+ * cases like the proto compiler. Other uses are discouraged and
525
+ * developers should rely on the protoreflect APIs for their client language.
526
+ */
527
+ features?: FeatureSet | undefined;
528
+ /**
529
+ * The parser stores options it doesn't recognize here.
530
+ * See the documentation for the "Options" section above.
531
+ */
532
+ uninterpretedOption: UninterpretedOption[];
533
+ }
534
+ /** Generated classes can be optimized for speed or code size. */
535
+ export declare enum FileOptions_OptimizeMode {
536
+ /** SPEED - Generate complete code for parsing, serialization, */
537
+ SPEED = 1,
538
+ /** CODE_SIZE - etc. */
539
+ CODE_SIZE = 2,
540
+ /** LITE_RUNTIME - Generate code using MessageLite and the lite runtime. */
541
+ LITE_RUNTIME = 3,
542
+ UNRECOGNIZED = -1
543
+ }
544
+ export declare function fileOptions_OptimizeModeFromJSON(object: any): FileOptions_OptimizeMode;
545
+ export declare function fileOptions_OptimizeModeToJSON(object: FileOptions_OptimizeMode): string;
546
+ export interface MessageOptions {
547
+ /**
548
+ * Set true to use the old proto1 MessageSet wire format for extensions.
549
+ * This is provided for backwards-compatibility with the MessageSet wire
550
+ * format. You should not use this for any other reason: It's less
551
+ * efficient, has fewer features, and is more complicated.
552
+ *
553
+ * The message must be defined exactly as follows:
554
+ * message Foo {
555
+ * option message_set_wire_format = true;
556
+ * extensions 4 to max;
557
+ * }
558
+ * Note that the message cannot have any defined fields; MessageSets only
559
+ * have extensions.
560
+ *
561
+ * All extensions of your type must be singular messages; e.g. they cannot
562
+ * be int32s, enums, or repeated messages.
563
+ *
564
+ * Because this is an option, the above two restrictions are not enforced by
565
+ * the protocol compiler.
566
+ */
567
+ messageSetWireFormat?: boolean | undefined;
568
+ /**
569
+ * Disables the generation of the standard "descriptor()" accessor, which can
570
+ * conflict with a field of the same name. This is meant to make migration
571
+ * from proto1 easier; new code should avoid fields named "descriptor".
572
+ */
573
+ noStandardDescriptorAccessor?: boolean | undefined;
574
+ /**
575
+ * Is this message deprecated?
576
+ * Depending on the target platform, this can emit Deprecated annotations
577
+ * for the message, or it will be completely ignored; in the very least,
578
+ * this is a formalization for deprecating messages.
579
+ */
580
+ deprecated?: boolean | undefined;
581
+ /**
582
+ * Whether the message is an automatically generated map entry type for the
583
+ * maps field.
584
+ *
585
+ * For maps fields:
586
+ * map<KeyType, ValueType> map_field = 1;
587
+ * The parsed descriptor looks like:
588
+ * message MapFieldEntry {
589
+ * option map_entry = true;
590
+ * optional KeyType key = 1;
591
+ * optional ValueType value = 2;
592
+ * }
593
+ * repeated MapFieldEntry map_field = 1;
594
+ *
595
+ * Implementations may choose not to generate the map_entry=true message, but
596
+ * use a native map in the target language to hold the keys and values.
597
+ * The reflection APIs in such implementations still need to work as
598
+ * if the field is a repeated message field.
599
+ *
600
+ * NOTE: Do not set the option in .proto files. Always use the maps syntax
601
+ * instead. The option should only be implicitly set by the proto compiler
602
+ * parser.
603
+ */
604
+ mapEntry?: boolean | undefined;
605
+ /**
606
+ * Enable the legacy handling of JSON field name conflicts. This lowercases
607
+ * and strips underscored from the fields before comparison in proto3 only.
608
+ * The new behavior takes `json_name` into account and applies to proto2 as
609
+ * well.
610
+ *
611
+ * This should only be used as a temporary measure against broken builds due
612
+ * to the change in behavior for JSON field name conflicts.
613
+ *
614
+ * TODO This is legacy behavior we plan to remove once downstream
615
+ * teams have had time to migrate.
616
+ *
617
+ * @deprecated
618
+ */
619
+ deprecatedLegacyJsonFieldConflicts?: boolean | undefined;
620
+ /**
621
+ * Any features defined in the specific edition.
622
+ * WARNING: This field should only be used by protobuf plugins or special
623
+ * cases like the proto compiler. Other uses are discouraged and
624
+ * developers should rely on the protoreflect APIs for their client language.
625
+ */
626
+ features?: FeatureSet | undefined;
627
+ /** The parser stores options it doesn't recognize here. See above. */
628
+ uninterpretedOption: UninterpretedOption[];
629
+ }
630
+ export interface FieldOptions {
631
+ /**
632
+ * NOTE: ctype is deprecated. Use `features.(pb.cpp).string_type` instead.
633
+ * The ctype option instructs the C++ code generator to use a different
634
+ * representation of the field than it normally would. See the specific
635
+ * options below. This option is only implemented to support use of
636
+ * [ctype=CORD] and [ctype=STRING] (the default) on non-repeated fields of
637
+ * type "bytes" in the open source release.
638
+ * TODO: make ctype actually deprecated.
639
+ */
640
+ ctype?: FieldOptions_CType | undefined;
641
+ /**
642
+ * The packed option can be enabled for repeated primitive fields to enable
643
+ * a more efficient representation on the wire. Rather than repeatedly
644
+ * writing the tag and type for each element, the entire array is encoded as
645
+ * a single length-delimited blob. In proto3, only explicit setting it to
646
+ * false will avoid using packed encoding. This option is prohibited in
647
+ * Editions, but the `repeated_field_encoding` feature can be used to control
648
+ * the behavior.
649
+ */
650
+ packed?: boolean | undefined;
651
+ /**
652
+ * The jstype option determines the JavaScript type used for values of the
653
+ * field. The option is permitted only for 64 bit integral and fixed types
654
+ * (int64, uint64, sint64, fixed64, sfixed64). A field with jstype JS_STRING
655
+ * is represented as JavaScript string, which avoids loss of precision that
656
+ * can happen when a large value is converted to a floating point JavaScript.
657
+ * Specifying JS_NUMBER for the jstype causes the generated JavaScript code to
658
+ * use the JavaScript "number" type. The behavior of the default option
659
+ * JS_NORMAL is implementation dependent.
660
+ *
661
+ * This option is an enum to permit additional types to be added, e.g.
662
+ * goog.math.Integer.
663
+ */
664
+ jstype?: FieldOptions_JSType | undefined;
665
+ /**
666
+ * Should this field be parsed lazily? Lazy applies only to message-type
667
+ * fields. It means that when the outer message is initially parsed, the
668
+ * inner message's contents will not be parsed but instead stored in encoded
669
+ * form. The inner message will actually be parsed when it is first accessed.
670
+ *
671
+ * This is only a hint. Implementations are free to choose whether to use
672
+ * eager or lazy parsing regardless of the value of this option. However,
673
+ * setting this option true suggests that the protocol author believes that
674
+ * using lazy parsing on this field is worth the additional bookkeeping
675
+ * overhead typically needed to implement it.
676
+ *
677
+ * This option does not affect the public interface of any generated code;
678
+ * all method signatures remain the same. Furthermore, thread-safety of the
679
+ * interface is not affected by this option; const methods remain safe to
680
+ * call from multiple threads concurrently, while non-const methods continue
681
+ * to require exclusive access.
682
+ *
683
+ * Note that lazy message fields are still eagerly verified to check
684
+ * ill-formed wireformat or missing required fields. Calling IsInitialized()
685
+ * on the outer message would fail if the inner message has missing required
686
+ * fields. Failed verification would result in parsing failure (except when
687
+ * uninitialized messages are acceptable).
688
+ */
689
+ lazy?: boolean | undefined;
690
+ /**
691
+ * unverified_lazy does no correctness checks on the byte stream. This should
692
+ * only be used where lazy with verification is prohibitive for performance
693
+ * reasons.
694
+ */
695
+ unverifiedLazy?: boolean | undefined;
696
+ /**
697
+ * Is this field deprecated?
698
+ * Depending on the target platform, this can emit Deprecated annotations
699
+ * for accessors, or it will be completely ignored; in the very least, this
700
+ * is a formalization for deprecating fields.
701
+ */
702
+ deprecated?: boolean | undefined;
703
+ /**
704
+ * DEPRECATED. DO NOT USE!
705
+ * For Google-internal migration only. Do not use.
706
+ *
707
+ * @deprecated
708
+ */
709
+ weak?: boolean | undefined;
710
+ /**
711
+ * Indicate that the field value should not be printed out when using debug
712
+ * formats, e.g. when the field contains sensitive credentials.
713
+ */
714
+ debugRedact?: boolean | undefined;
715
+ retention?: FieldOptions_OptionRetention | undefined;
716
+ targets: FieldOptions_OptionTargetType[];
717
+ editionDefaults: FieldOptions_EditionDefault[];
718
+ /**
719
+ * Any features defined in the specific edition.
720
+ * WARNING: This field should only be used by protobuf plugins or special
721
+ * cases like the proto compiler. Other uses are discouraged and
722
+ * developers should rely on the protoreflect APIs for their client language.
723
+ */
724
+ features?: FeatureSet | undefined;
725
+ featureSupport?: FieldOptions_FeatureSupport | undefined;
726
+ /** The parser stores options it doesn't recognize here. See above. */
727
+ uninterpretedOption: UninterpretedOption[];
728
+ }
729
+ export declare enum FieldOptions_CType {
730
+ /** STRING - Default mode. */
731
+ STRING = 0,
732
+ /**
733
+ * CORD - The option [ctype=CORD] may be applied to a non-repeated field of type
734
+ * "bytes". It indicates that in C++, the data should be stored in a Cord
735
+ * instead of a string. For very large strings, this may reduce memory
736
+ * fragmentation. It may also allow better performance when parsing from a
737
+ * Cord, or when parsing with aliasing enabled, as the parsed Cord may then
738
+ * alias the original buffer.
739
+ */
740
+ CORD = 1,
741
+ STRING_PIECE = 2,
742
+ UNRECOGNIZED = -1
743
+ }
744
+ export declare function fieldOptions_CTypeFromJSON(object: any): FieldOptions_CType;
745
+ export declare function fieldOptions_CTypeToJSON(object: FieldOptions_CType): string;
746
+ export declare enum FieldOptions_JSType {
747
+ /** JS_NORMAL - Use the default type. */
748
+ JS_NORMAL = 0,
749
+ /** JS_STRING - Use JavaScript strings. */
750
+ JS_STRING = 1,
751
+ /** JS_NUMBER - Use JavaScript numbers. */
752
+ JS_NUMBER = 2,
753
+ UNRECOGNIZED = -1
754
+ }
755
+ export declare function fieldOptions_JSTypeFromJSON(object: any): FieldOptions_JSType;
756
+ export declare function fieldOptions_JSTypeToJSON(object: FieldOptions_JSType): string;
757
+ /** If set to RETENTION_SOURCE, the option will be omitted from the binary. */
758
+ export declare enum FieldOptions_OptionRetention {
759
+ RETENTION_UNKNOWN = 0,
760
+ RETENTION_RUNTIME = 1,
761
+ RETENTION_SOURCE = 2,
762
+ UNRECOGNIZED = -1
763
+ }
764
+ export declare function fieldOptions_OptionRetentionFromJSON(object: any): FieldOptions_OptionRetention;
765
+ export declare function fieldOptions_OptionRetentionToJSON(object: FieldOptions_OptionRetention): string;
766
+ /**
767
+ * This indicates the types of entities that the field may apply to when used
768
+ * as an option. If it is unset, then the field may be freely used as an
769
+ * option on any kind of entity.
770
+ */
771
+ export declare enum FieldOptions_OptionTargetType {
772
+ TARGET_TYPE_UNKNOWN = 0,
773
+ TARGET_TYPE_FILE = 1,
774
+ TARGET_TYPE_EXTENSION_RANGE = 2,
775
+ TARGET_TYPE_MESSAGE = 3,
776
+ TARGET_TYPE_FIELD = 4,
777
+ TARGET_TYPE_ONEOF = 5,
778
+ TARGET_TYPE_ENUM = 6,
779
+ TARGET_TYPE_ENUM_ENTRY = 7,
780
+ TARGET_TYPE_SERVICE = 8,
781
+ TARGET_TYPE_METHOD = 9,
782
+ UNRECOGNIZED = -1
783
+ }
784
+ export declare function fieldOptions_OptionTargetTypeFromJSON(object: any): FieldOptions_OptionTargetType;
785
+ export declare function fieldOptions_OptionTargetTypeToJSON(object: FieldOptions_OptionTargetType): string;
786
+ export interface FieldOptions_EditionDefault {
787
+ edition?: Edition | undefined;
788
+ /** Textproto value. */
789
+ value?: string | undefined;
790
+ }
791
+ /** Information about the support window of a feature. */
792
+ export interface FieldOptions_FeatureSupport {
793
+ /**
794
+ * The edition that this feature was first available in. In editions
795
+ * earlier than this one, the default assigned to EDITION_LEGACY will be
796
+ * used, and proto files will not be able to override it.
797
+ */
798
+ editionIntroduced?: Edition | undefined;
799
+ /**
800
+ * The edition this feature becomes deprecated in. Using this after this
801
+ * edition may trigger warnings.
802
+ */
803
+ editionDeprecated?: Edition | undefined;
804
+ /**
805
+ * The deprecation warning text if this feature is used after the edition it
806
+ * was marked deprecated in.
807
+ */
808
+ deprecationWarning?: string | undefined;
809
+ /**
810
+ * The edition this feature is no longer available in. In editions after
811
+ * this one, the last default assigned will be used, and proto files will
812
+ * not be able to override it.
813
+ */
814
+ editionRemoved?: Edition | undefined;
815
+ }
816
+ export interface OneofOptions {
817
+ /**
818
+ * Any features defined in the specific edition.
819
+ * WARNING: This field should only be used by protobuf plugins or special
820
+ * cases like the proto compiler. Other uses are discouraged and
821
+ * developers should rely on the protoreflect APIs for their client language.
822
+ */
823
+ features?: FeatureSet | undefined;
824
+ /** The parser stores options it doesn't recognize here. See above. */
825
+ uninterpretedOption: UninterpretedOption[];
826
+ }
827
+ export interface EnumOptions {
828
+ /**
829
+ * Set this option to true to allow mapping different tag names to the same
830
+ * value.
831
+ */
832
+ allowAlias?: boolean | undefined;
833
+ /**
834
+ * Is this enum deprecated?
835
+ * Depending on the target platform, this can emit Deprecated annotations
836
+ * for the enum, or it will be completely ignored; in the very least, this
837
+ * is a formalization for deprecating enums.
838
+ */
839
+ deprecated?: boolean | undefined;
840
+ /**
841
+ * Enable the legacy handling of JSON field name conflicts. This lowercases
842
+ * and strips underscored from the fields before comparison in proto3 only.
843
+ * The new behavior takes `json_name` into account and applies to proto2 as
844
+ * well.
845
+ * TODO Remove this legacy behavior once downstream teams have
846
+ * had time to migrate.
847
+ *
848
+ * @deprecated
849
+ */
850
+ deprecatedLegacyJsonFieldConflicts?: boolean | undefined;
851
+ /**
852
+ * Any features defined in the specific edition.
853
+ * WARNING: This field should only be used by protobuf plugins or special
854
+ * cases like the proto compiler. Other uses are discouraged and
855
+ * developers should rely on the protoreflect APIs for their client language.
856
+ */
857
+ features?: FeatureSet | undefined;
858
+ /** The parser stores options it doesn't recognize here. See above. */
859
+ uninterpretedOption: UninterpretedOption[];
860
+ }
861
+ export interface EnumValueOptions {
862
+ /**
863
+ * Is this enum value deprecated?
864
+ * Depending on the target platform, this can emit Deprecated annotations
865
+ * for the enum value, or it will be completely ignored; in the very least,
866
+ * this is a formalization for deprecating enum values.
867
+ */
868
+ deprecated?: boolean | undefined;
869
+ /**
870
+ * Any features defined in the specific edition.
871
+ * WARNING: This field should only be used by protobuf plugins or special
872
+ * cases like the proto compiler. Other uses are discouraged and
873
+ * developers should rely on the protoreflect APIs for their client language.
874
+ */
875
+ features?: FeatureSet | undefined;
876
+ /**
877
+ * Indicate that fields annotated with this enum value should not be printed
878
+ * out when using debug formats, e.g. when the field contains sensitive
879
+ * credentials.
880
+ */
881
+ debugRedact?: boolean | undefined;
882
+ /** Information about the support window of a feature value. */
883
+ featureSupport?: FieldOptions_FeatureSupport | undefined;
884
+ /** The parser stores options it doesn't recognize here. See above. */
885
+ uninterpretedOption: UninterpretedOption[];
886
+ }
887
+ export interface ServiceOptions {
888
+ /**
889
+ * Any features defined in the specific edition.
890
+ * WARNING: This field should only be used by protobuf plugins or special
891
+ * cases like the proto compiler. Other uses are discouraged and
892
+ * developers should rely on the protoreflect APIs for their client language.
893
+ */
894
+ features?: FeatureSet | undefined;
895
+ /**
896
+ * Is this service deprecated?
897
+ * Depending on the target platform, this can emit Deprecated annotations
898
+ * for the service, or it will be completely ignored; in the very least,
899
+ * this is a formalization for deprecating services.
900
+ */
901
+ deprecated?: boolean | undefined;
902
+ /** The parser stores options it doesn't recognize here. See above. */
903
+ uninterpretedOption: UninterpretedOption[];
904
+ }
905
+ export interface MethodOptions {
906
+ /**
907
+ * Is this method deprecated?
908
+ * Depending on the target platform, this can emit Deprecated annotations
909
+ * for the method, or it will be completely ignored; in the very least,
910
+ * this is a formalization for deprecating methods.
911
+ */
912
+ deprecated?: boolean | undefined;
913
+ idempotencyLevel?: MethodOptions_IdempotencyLevel | undefined;
914
+ /**
915
+ * Any features defined in the specific edition.
916
+ * WARNING: This field should only be used by protobuf plugins or special
917
+ * cases like the proto compiler. Other uses are discouraged and
918
+ * developers should rely on the protoreflect APIs for their client language.
919
+ */
920
+ features?: FeatureSet | undefined;
921
+ /** The parser stores options it doesn't recognize here. See above. */
922
+ uninterpretedOption: UninterpretedOption[];
923
+ }
924
+ /**
925
+ * Is this method side-effect-free (or safe in HTTP parlance), or idempotent,
926
+ * or neither? HTTP based RPC implementation may choose GET verb for safe
927
+ * methods, and PUT verb for idempotent methods instead of the default POST.
928
+ */
929
+ export declare enum MethodOptions_IdempotencyLevel {
930
+ IDEMPOTENCY_UNKNOWN = 0,
931
+ /** NO_SIDE_EFFECTS - implies idempotent */
932
+ NO_SIDE_EFFECTS = 1,
933
+ /** IDEMPOTENT - idempotent, but may have side effects */
934
+ IDEMPOTENT = 2,
935
+ UNRECOGNIZED = -1
936
+ }
937
+ export declare function methodOptions_IdempotencyLevelFromJSON(object: any): MethodOptions_IdempotencyLevel;
938
+ export declare function methodOptions_IdempotencyLevelToJSON(object: MethodOptions_IdempotencyLevel): string;
939
+ /**
940
+ * A message representing a option the parser does not recognize. This only
941
+ * appears in options protos created by the compiler::Parser class.
942
+ * DescriptorPool resolves these when building Descriptor objects. Therefore,
943
+ * options protos in descriptor objects (e.g. returned by Descriptor::options(),
944
+ * or produced by Descriptor::CopyTo()) will never have UninterpretedOptions
945
+ * in them.
946
+ */
947
+ export interface UninterpretedOption {
948
+ name: UninterpretedOption_NamePart[];
949
+ /**
950
+ * The value of the uninterpreted option, in whatever type the tokenizer
951
+ * identified it as during parsing. Exactly one of these should be set.
952
+ */
953
+ identifierValue?: string | undefined;
954
+ positiveIntValue?: number | undefined;
955
+ negativeIntValue?: number | undefined;
956
+ doubleValue?: number | undefined;
957
+ stringValue?: Uint8Array | undefined;
958
+ aggregateValue?: string | undefined;
959
+ }
960
+ /**
961
+ * The name of the uninterpreted option. Each string represents a segment in
962
+ * a dot-separated name. is_extension is true iff a segment represents an
963
+ * extension (denoted with parentheses in options specs in .proto files).
964
+ * E.g.,{ ["foo", false], ["bar.baz", true], ["moo", false] } represents
965
+ * "foo.(bar.baz).moo".
966
+ */
967
+ export interface UninterpretedOption_NamePart {
968
+ namePart: string;
969
+ isExtension: boolean;
970
+ }
971
+ /**
972
+ * TODO Enums in C++ gencode (and potentially other languages) are
973
+ * not well scoped. This means that each of the feature enums below can clash
974
+ * with each other. The short names we've chosen maximize call-site
975
+ * readability, but leave us very open to this scenario. A future feature will
976
+ * be designed and implemented to handle this, hopefully before we ever hit a
977
+ * conflict here.
978
+ */
979
+ export interface FeatureSet {
980
+ fieldPresence?: FeatureSet_FieldPresence | undefined;
981
+ enumType?: FeatureSet_EnumType | undefined;
982
+ repeatedFieldEncoding?: FeatureSet_RepeatedFieldEncoding | undefined;
983
+ utf8Validation?: FeatureSet_Utf8Validation | undefined;
984
+ messageEncoding?: FeatureSet_MessageEncoding | undefined;
985
+ jsonFormat?: FeatureSet_JsonFormat | undefined;
986
+ enforceNamingStyle?: FeatureSet_EnforceNamingStyle | undefined;
987
+ defaultSymbolVisibility?: FeatureSet_VisibilityFeature_DefaultSymbolVisibility | undefined;
988
+ }
989
+ export declare enum FeatureSet_FieldPresence {
990
+ FIELD_PRESENCE_UNKNOWN = 0,
991
+ EXPLICIT = 1,
992
+ IMPLICIT = 2,
993
+ LEGACY_REQUIRED = 3,
994
+ UNRECOGNIZED = -1
995
+ }
996
+ export declare function featureSet_FieldPresenceFromJSON(object: any): FeatureSet_FieldPresence;
997
+ export declare function featureSet_FieldPresenceToJSON(object: FeatureSet_FieldPresence): string;
998
+ export declare enum FeatureSet_EnumType {
999
+ ENUM_TYPE_UNKNOWN = 0,
1000
+ OPEN = 1,
1001
+ CLOSED = 2,
1002
+ UNRECOGNIZED = -1
1003
+ }
1004
+ export declare function featureSet_EnumTypeFromJSON(object: any): FeatureSet_EnumType;
1005
+ export declare function featureSet_EnumTypeToJSON(object: FeatureSet_EnumType): string;
1006
+ export declare enum FeatureSet_RepeatedFieldEncoding {
1007
+ REPEATED_FIELD_ENCODING_UNKNOWN = 0,
1008
+ PACKED = 1,
1009
+ EXPANDED = 2,
1010
+ UNRECOGNIZED = -1
1011
+ }
1012
+ export declare function featureSet_RepeatedFieldEncodingFromJSON(object: any): FeatureSet_RepeatedFieldEncoding;
1013
+ export declare function featureSet_RepeatedFieldEncodingToJSON(object: FeatureSet_RepeatedFieldEncoding): string;
1014
+ export declare enum FeatureSet_Utf8Validation {
1015
+ UTF8_VALIDATION_UNKNOWN = 0,
1016
+ VERIFY = 2,
1017
+ NONE = 3,
1018
+ UNRECOGNIZED = -1
1019
+ }
1020
+ export declare function featureSet_Utf8ValidationFromJSON(object: any): FeatureSet_Utf8Validation;
1021
+ export declare function featureSet_Utf8ValidationToJSON(object: FeatureSet_Utf8Validation): string;
1022
+ export declare enum FeatureSet_MessageEncoding {
1023
+ MESSAGE_ENCODING_UNKNOWN = 0,
1024
+ LENGTH_PREFIXED = 1,
1025
+ DELIMITED = 2,
1026
+ UNRECOGNIZED = -1
1027
+ }
1028
+ export declare function featureSet_MessageEncodingFromJSON(object: any): FeatureSet_MessageEncoding;
1029
+ export declare function featureSet_MessageEncodingToJSON(object: FeatureSet_MessageEncoding): string;
1030
+ export declare enum FeatureSet_JsonFormat {
1031
+ JSON_FORMAT_UNKNOWN = 0,
1032
+ ALLOW = 1,
1033
+ LEGACY_BEST_EFFORT = 2,
1034
+ UNRECOGNIZED = -1
1035
+ }
1036
+ export declare function featureSet_JsonFormatFromJSON(object: any): FeatureSet_JsonFormat;
1037
+ export declare function featureSet_JsonFormatToJSON(object: FeatureSet_JsonFormat): string;
1038
+ export declare enum FeatureSet_EnforceNamingStyle {
1039
+ ENFORCE_NAMING_STYLE_UNKNOWN = 0,
1040
+ STYLE2024 = 1,
1041
+ STYLE_LEGACY = 2,
1042
+ UNRECOGNIZED = -1
1043
+ }
1044
+ export declare function featureSet_EnforceNamingStyleFromJSON(object: any): FeatureSet_EnforceNamingStyle;
1045
+ export declare function featureSet_EnforceNamingStyleToJSON(object: FeatureSet_EnforceNamingStyle): string;
1046
+ export interface FeatureSet_VisibilityFeature {
1047
+ }
1048
+ export declare enum FeatureSet_VisibilityFeature_DefaultSymbolVisibility {
1049
+ DEFAULT_SYMBOL_VISIBILITY_UNKNOWN = 0,
1050
+ /** EXPORT_ALL - Default pre-EDITION_2024, all UNSET visibility are export. */
1051
+ EXPORT_ALL = 1,
1052
+ /** EXPORT_TOP_LEVEL - All top-level symbols default to export, nested default to local. */
1053
+ EXPORT_TOP_LEVEL = 2,
1054
+ /** LOCAL_ALL - All symbols default to local. */
1055
+ LOCAL_ALL = 3,
1056
+ /**
1057
+ * STRICT - All symbols local by default. Nested types cannot be exported.
1058
+ * With special case caveat for message { enum {} reserved 1 to max; }
1059
+ * This is the recommended setting for new protos.
1060
+ */
1061
+ STRICT = 4,
1062
+ UNRECOGNIZED = -1
1063
+ }
1064
+ export declare function featureSet_VisibilityFeature_DefaultSymbolVisibilityFromJSON(object: any): FeatureSet_VisibilityFeature_DefaultSymbolVisibility;
1065
+ export declare function featureSet_VisibilityFeature_DefaultSymbolVisibilityToJSON(object: FeatureSet_VisibilityFeature_DefaultSymbolVisibility): string;
1066
+ /**
1067
+ * A compiled specification for the defaults of a set of features. These
1068
+ * messages are generated from FeatureSet extensions and can be used to seed
1069
+ * feature resolution. The resolution with this object becomes a simple search
1070
+ * for the closest matching edition, followed by proto merges.
1071
+ */
1072
+ export interface FeatureSetDefaults {
1073
+ defaults: FeatureSetDefaults_FeatureSetEditionDefault[];
1074
+ /**
1075
+ * The minimum supported edition (inclusive) when this was constructed.
1076
+ * Editions before this will not have defaults.
1077
+ */
1078
+ minimumEdition?: Edition | undefined;
1079
+ /**
1080
+ * The maximum known edition (inclusive) when this was constructed. Editions
1081
+ * after this will not have reliable defaults.
1082
+ */
1083
+ maximumEdition?: Edition | undefined;
1084
+ }
1085
+ /**
1086
+ * A map from every known edition with a unique set of defaults to its
1087
+ * defaults. Not all editions may be contained here. For a given edition,
1088
+ * the defaults at the closest matching edition ordered at or before it should
1089
+ * be used. This field must be in strict ascending order by edition.
1090
+ */
1091
+ export interface FeatureSetDefaults_FeatureSetEditionDefault {
1092
+ edition?: Edition | undefined;
1093
+ /** Defaults of features that can be overridden in this edition. */
1094
+ overridableFeatures?: FeatureSet | undefined;
1095
+ /** Defaults of features that can't be overridden in this edition. */
1096
+ fixedFeatures?: FeatureSet | undefined;
1097
+ }
1098
+ /**
1099
+ * Encapsulates information about the original source file from which a
1100
+ * FileDescriptorProto was generated.
1101
+ */
1102
+ export interface SourceCodeInfo {
1103
+ /**
1104
+ * A Location identifies a piece of source code in a .proto file which
1105
+ * corresponds to a particular definition. This information is intended
1106
+ * to be useful to IDEs, code indexers, documentation generators, and similar
1107
+ * tools.
1108
+ *
1109
+ * For example, say we have a file like:
1110
+ * message Foo {
1111
+ * optional string foo = 1;
1112
+ * }
1113
+ * Let's look at just the field definition:
1114
+ * optional string foo = 1;
1115
+ * ^ ^^ ^^ ^ ^^^
1116
+ * a bc de f ghi
1117
+ * We have the following locations:
1118
+ * span path represents
1119
+ * [a,i) [ 4, 0, 2, 0 ] The whole field definition.
1120
+ * [a,b) [ 4, 0, 2, 0, 4 ] The label (optional).
1121
+ * [c,d) [ 4, 0, 2, 0, 5 ] The type (string).
1122
+ * [e,f) [ 4, 0, 2, 0, 1 ] The name (foo).
1123
+ * [g,h) [ 4, 0, 2, 0, 3 ] The number (1).
1124
+ *
1125
+ * Notes:
1126
+ * - A location may refer to a repeated field itself (i.e. not to any
1127
+ * particular index within it). This is used whenever a set of elements are
1128
+ * logically enclosed in a single code segment. For example, an entire
1129
+ * extend block (possibly containing multiple extension definitions) will
1130
+ * have an outer location whose path refers to the "extensions" repeated
1131
+ * field without an index.
1132
+ * - Multiple locations may have the same path. This happens when a single
1133
+ * logical declaration is spread out across multiple places. The most
1134
+ * obvious example is the "extend" block again -- there may be multiple
1135
+ * extend blocks in the same scope, each of which will have the same path.
1136
+ * - A location's span is not always a subset of its parent's span. For
1137
+ * example, the "extendee" of an extension declaration appears at the
1138
+ * beginning of the "extend" block and is shared by all extensions within
1139
+ * the block.
1140
+ * - Just because a location's span is a subset of some other location's span
1141
+ * does not mean that it is a descendant. For example, a "group" defines
1142
+ * both a type and a field in a single declaration. Thus, the locations
1143
+ * corresponding to the type and field and their components will overlap.
1144
+ * - Code which tries to interpret locations should probably be designed to
1145
+ * ignore those that it doesn't understand, as more types of locations could
1146
+ * be recorded in the future.
1147
+ */
1148
+ location: SourceCodeInfo_Location[];
1149
+ }
1150
+ export interface SourceCodeInfo_Location {
1151
+ /**
1152
+ * Identifies which part of the FileDescriptorProto was defined at this
1153
+ * location.
1154
+ *
1155
+ * Each element is a field number or an index. They form a path from
1156
+ * the root FileDescriptorProto to the place where the definition appears.
1157
+ * For example, this path:
1158
+ * [ 4, 3, 2, 7, 1 ]
1159
+ * refers to:
1160
+ * file.message_type(3) // 4, 3
1161
+ * .field(7) // 2, 7
1162
+ * .name() // 1
1163
+ * This is because FileDescriptorProto.message_type has field number 4:
1164
+ * repeated DescriptorProto message_type = 4;
1165
+ * and DescriptorProto.field has field number 2:
1166
+ * repeated FieldDescriptorProto field = 2;
1167
+ * and FieldDescriptorProto.name has field number 1:
1168
+ * optional string name = 1;
1169
+ *
1170
+ * Thus, the above path gives the location of a field name. If we removed
1171
+ * the last element:
1172
+ * [ 4, 3, 2, 7 ]
1173
+ * this path refers to the whole field declaration (from the beginning
1174
+ * of the label to the terminating semicolon).
1175
+ */
1176
+ path: number[];
1177
+ /**
1178
+ * Always has exactly three or four elements: start line, start column,
1179
+ * end line (optional, otherwise assumed same as start line), end column.
1180
+ * These are packed into a single field for efficiency. Note that line
1181
+ * and column numbers are zero-based -- typically you will want to add
1182
+ * 1 to each before displaying to a user.
1183
+ */
1184
+ span: number[];
1185
+ /**
1186
+ * If this SourceCodeInfo represents a complete declaration, these are any
1187
+ * comments appearing before and after the declaration which appear to be
1188
+ * attached to the declaration.
1189
+ *
1190
+ * A series of line comments appearing on consecutive lines, with no other
1191
+ * tokens appearing on those lines, will be treated as a single comment.
1192
+ *
1193
+ * leading_detached_comments will keep paragraphs of comments that appear
1194
+ * before (but not connected to) the current element. Each paragraph,
1195
+ * separated by empty lines, will be one comment element in the repeated
1196
+ * field.
1197
+ *
1198
+ * Only the comment content is provided; comment markers (e.g. //) are
1199
+ * stripped out. For block comments, leading whitespace and an asterisk
1200
+ * will be stripped from the beginning of each line other than the first.
1201
+ * Newlines are included in the output.
1202
+ *
1203
+ * Examples:
1204
+ *
1205
+ * optional int32 foo = 1; // Comment attached to foo.
1206
+ * // Comment attached to bar.
1207
+ * optional int32 bar = 2;
1208
+ *
1209
+ * optional string baz = 3;
1210
+ * // Comment attached to baz.
1211
+ * // Another line attached to baz.
1212
+ *
1213
+ * // Comment attached to moo.
1214
+ * //
1215
+ * // Another line attached to moo.
1216
+ * optional double moo = 4;
1217
+ *
1218
+ * // Detached comment for corge. This is not leading or trailing comments
1219
+ * // to moo or corge because there are blank lines separating it from
1220
+ * // both.
1221
+ *
1222
+ * // Detached comment for corge paragraph 2.
1223
+ *
1224
+ * optional string corge = 5;
1225
+ * /* Block comment attached
1226
+ * * to corge. Leading asterisks
1227
+ * * will be removed. * /
1228
+ * /* Block comment attached to
1229
+ * * grault. * /
1230
+ * optional int32 grault = 6;
1231
+ *
1232
+ * // ignored detached comments.
1233
+ */
1234
+ leadingComments?: string | undefined;
1235
+ trailingComments?: string | undefined;
1236
+ leadingDetachedComments: string[];
1237
+ }
1238
+ /**
1239
+ * Describes the relationship between generated code and its original source
1240
+ * file. A GeneratedCodeInfo message is associated with only one generated
1241
+ * source file, but may contain references to different source .proto files.
1242
+ */
1243
+ export interface GeneratedCodeInfo {
1244
+ /**
1245
+ * An Annotation connects some span of text in generated code to an element
1246
+ * of its generating .proto file.
1247
+ */
1248
+ annotation: GeneratedCodeInfo_Annotation[];
1249
+ }
1250
+ export interface GeneratedCodeInfo_Annotation {
1251
+ /**
1252
+ * Identifies the element in the original source .proto file. This field
1253
+ * is formatted the same as SourceCodeInfo.Location.path.
1254
+ */
1255
+ path: number[];
1256
+ /** Identifies the filesystem path to the original source .proto. */
1257
+ sourceFile?: string | undefined;
1258
+ /**
1259
+ * Identifies the starting offset in bytes in the generated code
1260
+ * that relates to the identified object.
1261
+ */
1262
+ begin?: number | undefined;
1263
+ /**
1264
+ * Identifies the ending offset in bytes in the generated code that
1265
+ * relates to the identified object. The end offset should be one past
1266
+ * the last relevant byte (so the length of the text = end - begin).
1267
+ */
1268
+ end?: number | undefined;
1269
+ semantic?: GeneratedCodeInfo_Annotation_Semantic | undefined;
1270
+ }
1271
+ /**
1272
+ * Represents the identified object's effect on the element in the original
1273
+ * .proto file.
1274
+ */
1275
+ export declare enum GeneratedCodeInfo_Annotation_Semantic {
1276
+ /** NONE - There is no effect or the effect is indescribable. */
1277
+ NONE = 0,
1278
+ /** SET - The element is set or otherwise mutated. */
1279
+ SET = 1,
1280
+ /** ALIAS - An alias to the element is returned. */
1281
+ ALIAS = 2,
1282
+ UNRECOGNIZED = -1
1283
+ }
1284
+ export declare function generatedCodeInfo_Annotation_SemanticFromJSON(object: any): GeneratedCodeInfo_Annotation_Semantic;
1285
+ export declare function generatedCodeInfo_Annotation_SemanticToJSON(object: GeneratedCodeInfo_Annotation_Semantic): string;
1286
+ export declare const FileDescriptorSet: MessageFns<FileDescriptorSet>;
1287
+ export declare const FileDescriptorProto: MessageFns<FileDescriptorProto>;
1288
+ export declare const DescriptorProto: MessageFns<DescriptorProto>;
1289
+ export declare const DescriptorProto_ExtensionRange: MessageFns<DescriptorProto_ExtensionRange>;
1290
+ export declare const DescriptorProto_ReservedRange: MessageFns<DescriptorProto_ReservedRange>;
1291
+ export declare const ExtensionRangeOptions: MessageFns<ExtensionRangeOptions>;
1292
+ export declare const ExtensionRangeOptions_Declaration: MessageFns<ExtensionRangeOptions_Declaration>;
1293
+ export declare const FieldDescriptorProto: MessageFns<FieldDescriptorProto>;
1294
+ export declare const OneofDescriptorProto: MessageFns<OneofDescriptorProto>;
1295
+ export declare const EnumDescriptorProto: MessageFns<EnumDescriptorProto>;
1296
+ export declare const EnumDescriptorProto_EnumReservedRange: MessageFns<EnumDescriptorProto_EnumReservedRange>;
1297
+ export declare const EnumValueDescriptorProto: MessageFns<EnumValueDescriptorProto>;
1298
+ export declare const ServiceDescriptorProto: MessageFns<ServiceDescriptorProto>;
1299
+ export declare const MethodDescriptorProto: MessageFns<MethodDescriptorProto>;
1300
+ export declare const FileOptions: MessageFns<FileOptions>;
1301
+ export declare const MessageOptions: MessageFns<MessageOptions>;
1302
+ export declare const FieldOptions: MessageFns<FieldOptions>;
1303
+ export declare const FieldOptions_EditionDefault: MessageFns<FieldOptions_EditionDefault>;
1304
+ export declare const FieldOptions_FeatureSupport: MessageFns<FieldOptions_FeatureSupport>;
1305
+ export declare const OneofOptions: MessageFns<OneofOptions>;
1306
+ export declare const EnumOptions: MessageFns<EnumOptions>;
1307
+ export declare const EnumValueOptions: MessageFns<EnumValueOptions>;
1308
+ export declare const ServiceOptions: MessageFns<ServiceOptions>;
1309
+ export declare const MethodOptions: MessageFns<MethodOptions>;
1310
+ export declare const UninterpretedOption: MessageFns<UninterpretedOption>;
1311
+ export declare const UninterpretedOption_NamePart: MessageFns<UninterpretedOption_NamePart>;
1312
+ export declare const FeatureSet: MessageFns<FeatureSet>;
1313
+ export declare const FeatureSet_VisibilityFeature: MessageFns<FeatureSet_VisibilityFeature>;
1314
+ export declare const FeatureSetDefaults: MessageFns<FeatureSetDefaults>;
1315
+ export declare const FeatureSetDefaults_FeatureSetEditionDefault: MessageFns<FeatureSetDefaults_FeatureSetEditionDefault>;
1316
+ export declare const SourceCodeInfo: MessageFns<SourceCodeInfo>;
1317
+ export declare const SourceCodeInfo_Location: MessageFns<SourceCodeInfo_Location>;
1318
+ export declare const GeneratedCodeInfo: MessageFns<GeneratedCodeInfo>;
1319
+ export declare const GeneratedCodeInfo_Annotation: MessageFns<GeneratedCodeInfo_Annotation>;
1320
+ type Builtin = Date | Function | Uint8Array | string | number | boolean | undefined;
1321
+ export type DeepPartial<T> = T extends Builtin ? T : T extends globalThis.Array<infer U> ? globalThis.Array<DeepPartial<U>> : T extends ReadonlyArray<infer U> ? ReadonlyArray<DeepPartial<U>> : T extends {} ? {
1322
+ [K in keyof T]?: DeepPartial<T[K]>;
1323
+ } : Partial<T>;
1324
+ type KeysOfUnion<T> = T extends T ? keyof T : never;
1325
+ export type Exact<P, I extends P> = P extends Builtin ? P : P & {
1326
+ [K in keyof P]: Exact<P[K], I[K]>;
1327
+ } & {
1328
+ [K in Exclude<keyof I, KeysOfUnion<P>>]: never;
1329
+ };
1330
+ export interface MessageFns<T> {
1331
+ encode(message: T, writer?: BinaryWriter): BinaryWriter;
1332
+ decode(input: BinaryReader | Uint8Array, length?: number): T;
1333
+ fromJSON(object: any): T;
1334
+ toJSON(message: T): unknown;
1335
+ create<I extends Exact<DeepPartial<T>, I>>(base?: I): T;
1336
+ fromPartial<I extends Exact<DeepPartial<T>, I>>(object: I): T;
1337
+ }
1338
+ export {};