weave-typescript 0.1.0

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