@milaboratories/pl-client 2.4.10 → 2.4.11

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 (101) hide show
  1. package/dist/core/auth.d.ts +6 -0
  2. package/dist/core/auth.d.ts.map +1 -0
  3. package/dist/core/client.d.ts +50 -0
  4. package/dist/core/client.d.ts.map +1 -0
  5. package/dist/core/config.d.ts +91 -0
  6. package/dist/core/config.d.ts.map +1 -0
  7. package/dist/core/default_client.d.ts +11 -0
  8. package/dist/core/default_client.d.ts.map +1 -0
  9. package/dist/core/driver.d.ts +18 -0
  10. package/dist/core/driver.d.ts.map +1 -0
  11. package/dist/core/errors.d.ts +25 -0
  12. package/dist/core/errors.d.ts.map +1 -0
  13. package/dist/core/http.d.ts +1 -0
  14. package/dist/core/http.d.ts.map +1 -0
  15. package/dist/core/ll_client.d.ts +50 -0
  16. package/dist/core/ll_client.d.ts.map +1 -0
  17. package/dist/core/ll_transaction.d.ts +55 -0
  18. package/dist/core/ll_transaction.d.ts.map +1 -0
  19. package/dist/core/transaction.d.ts +152 -0
  20. package/dist/core/transaction.d.ts.map +1 -0
  21. package/dist/core/type_conversion.d.ts +8 -0
  22. package/dist/core/type_conversion.d.ts.map +1 -0
  23. package/dist/core/types.d.ts +77 -0
  24. package/dist/core/types.d.ts.map +1 -0
  25. package/dist/core/unauth_client.d.ts +13 -0
  26. package/dist/core/unauth_client.d.ts.map +1 -0
  27. package/dist/helpers/pl.d.ts +34 -0
  28. package/dist/helpers/pl.d.ts.map +1 -0
  29. package/dist/helpers/poll.d.ts +39 -0
  30. package/dist/helpers/poll.d.ts.map +1 -0
  31. package/dist/helpers/rich_resource_types.d.ts +1 -0
  32. package/dist/helpers/rich_resource_types.d.ts.map +1 -0
  33. package/dist/helpers/smart_accessors.d.ts +1 -0
  34. package/dist/helpers/smart_accessors.d.ts.map +1 -0
  35. package/dist/helpers/state_helpers.d.ts +3 -0
  36. package/dist/helpers/state_helpers.d.ts.map +1 -0
  37. package/dist/helpers/tx_helpers.d.ts +9 -0
  38. package/dist/helpers/tx_helpers.d.ts.map +1 -0
  39. package/dist/index.d.ts +14 -0
  40. package/dist/index.d.ts.map +1 -0
  41. package/dist/index.js +1 -14425
  42. package/dist/index.js.map +1 -1
  43. package/dist/index.mjs +12126 -0
  44. package/dist/index.mjs.map +1 -0
  45. package/dist/proto/github.com/googleapis/googleapis/google/rpc/status.d.ts +48 -0
  46. package/dist/proto/github.com/googleapis/googleapis/google/rpc/status.d.ts.map +1 -0
  47. package/dist/proto/github.com/milaboratory/pl/controllers/shared/grpc/downloadapi/protocol.client.d.ts +36 -0
  48. package/dist/proto/github.com/milaboratory/pl/controllers/shared/grpc/downloadapi/protocol.client.d.ts.map +1 -0
  49. package/dist/proto/github.com/milaboratory/pl/controllers/shared/grpc/downloadapi/protocol.d.ts +103 -0
  50. package/dist/proto/github.com/milaboratory/pl/controllers/shared/grpc/downloadapi/protocol.d.ts.map +1 -0
  51. package/dist/proto/github.com/milaboratory/pl/controllers/shared/grpc/lsapi/protocol.client.d.ts +42 -0
  52. package/dist/proto/github.com/milaboratory/pl/controllers/shared/grpc/lsapi/protocol.client.d.ts.map +1 -0
  53. package/dist/proto/github.com/milaboratory/pl/controllers/shared/grpc/lsapi/protocol.d.ts +165 -0
  54. package/dist/proto/github.com/milaboratory/pl/controllers/shared/grpc/lsapi/protocol.d.ts.map +1 -0
  55. package/dist/proto/github.com/milaboratory/pl/controllers/shared/grpc/progressapi/protocol.client.d.ts +44 -0
  56. package/dist/proto/github.com/milaboratory/pl/controllers/shared/grpc/progressapi/protocol.client.d.ts.map +1 -0
  57. package/dist/proto/github.com/milaboratory/pl/controllers/shared/grpc/progressapi/protocol.d.ts +171 -0
  58. package/dist/proto/github.com/milaboratory/pl/controllers/shared/grpc/progressapi/protocol.d.ts.map +1 -0
  59. package/dist/proto/github.com/milaboratory/pl/controllers/shared/grpc/streamingapi/protocol.client.d.ts +122 -0
  60. package/dist/proto/github.com/milaboratory/pl/controllers/shared/grpc/streamingapi/protocol.client.d.ts.map +1 -0
  61. package/dist/proto/github.com/milaboratory/pl/controllers/shared/grpc/streamingapi/protocol.d.ts +315 -0
  62. package/dist/proto/github.com/milaboratory/pl/controllers/shared/grpc/streamingapi/protocol.d.ts.map +1 -0
  63. package/dist/proto/github.com/milaboratory/pl/plapi/plapiproto/api.client.d.ts +276 -0
  64. package/dist/proto/github.com/milaboratory/pl/plapi/plapiproto/api.client.d.ts.map +1 -0
  65. package/dist/proto/github.com/milaboratory/pl/plapi/plapiproto/api.d.ts +5045 -0
  66. package/dist/proto/github.com/milaboratory/pl/plapi/plapiproto/api.d.ts.map +1 -0
  67. package/dist/proto/github.com/milaboratory/pl/plapi/plapiproto/api_types.d.ts +499 -0
  68. package/dist/proto/github.com/milaboratory/pl/plapi/plapiproto/api_types.d.ts.map +1 -0
  69. package/dist/proto/github.com/milaboratory/pl/plapi/plapiproto/base_types.d.ts +82 -0
  70. package/dist/proto/github.com/milaboratory/pl/plapi/plapiproto/base_types.d.ts.map +1 -0
  71. package/dist/proto/github.com/milaboratory/pl/plapi/plapiproto/import.d.ts +91 -0
  72. package/dist/proto/github.com/milaboratory/pl/plapi/plapiproto/import.d.ts.map +1 -0
  73. package/dist/proto/github.com/milaboratory/pl/plapi/plapiproto/resource_types.d.ts +251 -0
  74. package/dist/proto/github.com/milaboratory/pl/plapi/plapiproto/resource_types.d.ts.map +1 -0
  75. package/dist/proto/google/api/http.d.ts +451 -0
  76. package/dist/proto/google/api/http.d.ts.map +1 -0
  77. package/dist/proto/google/protobuf/any.d.ts +172 -0
  78. package/dist/proto/google/protobuf/any.d.ts.map +1 -0
  79. package/dist/proto/google/protobuf/descriptor.d.ts +2258 -0
  80. package/dist/proto/google/protobuf/descriptor.d.ts.map +1 -0
  81. package/dist/proto/google/protobuf/duration.d.ts +105 -0
  82. package/dist/proto/google/protobuf/duration.d.ts.map +1 -0
  83. package/dist/proto/google/protobuf/empty.d.ts +27 -0
  84. package/dist/proto/google/protobuf/empty.d.ts.map +1 -0
  85. package/dist/proto/google/protobuf/struct.d.ts +177 -0
  86. package/dist/proto/google/protobuf/struct.d.ts.map +1 -0
  87. package/dist/proto/google/protobuf/timestamp.d.ts +148 -0
  88. package/dist/proto/google/protobuf/timestamp.d.ts.map +1 -0
  89. package/dist/proto/google/protobuf/wrappers.d.ts +300 -0
  90. package/dist/proto/google/protobuf/wrappers.d.ts.map +1 -0
  91. package/dist/test/test_config.d.ts +18 -0
  92. package/dist/test/test_config.d.ts.map +1 -0
  93. package/dist/util/branding.d.ts +7 -0
  94. package/dist/util/branding.d.ts.map +1 -0
  95. package/dist/util/pl.d.ts +9 -0
  96. package/dist/util/pl.d.ts.map +1 -0
  97. package/dist/util/util.d.ts +2 -0
  98. package/dist/util/util.d.ts.map +1 -0
  99. package/package.json +10 -14
  100. package/dist/index.cjs +0 -14527
  101. package/dist/index.cjs.map +0 -1
@@ -0,0 +1,451 @@
1
+ import { BinaryWriteOptions, IBinaryWriter, BinaryReadOptions, IBinaryReader, PartialMessage, MessageType } from '@protobuf-ts/runtime';
2
+ /**
3
+ * Defines the HTTP configuration for an API service. It contains a list of
4
+ * [HttpRule][google.api.HttpRule], each specifying the mapping of an RPC method
5
+ * to one or more HTTP REST API methods.
6
+ *
7
+ * @generated from protobuf message google.api.Http
8
+ */
9
+ export interface Http {
10
+ /**
11
+ * A list of HTTP configuration rules that apply to individual API methods.
12
+ *
13
+ * **NOTE:** All service configuration rules follow "last one wins" order.
14
+ *
15
+ * @generated from protobuf field: repeated google.api.HttpRule rules = 1;
16
+ */
17
+ rules: HttpRule[];
18
+ /**
19
+ * When set to true, URL path parameters will be fully URI-decoded except in
20
+ * cases of single segment matches in reserved expansion, where "%2F" will be
21
+ * left encoded.
22
+ *
23
+ * The default behavior is to not decode RFC 6570 reserved characters in multi
24
+ * segment matches.
25
+ *
26
+ * @generated from protobuf field: bool fully_decode_reserved_expansion = 2;
27
+ */
28
+ fullyDecodeReservedExpansion: boolean;
29
+ }
30
+ /**
31
+ * # gRPC Transcoding
32
+ *
33
+ * gRPC Transcoding is a feature for mapping between a gRPC method and one or
34
+ * more HTTP REST endpoints. It allows developers to build a single API service
35
+ * that supports both gRPC APIs and REST APIs. Many systems, including [Google
36
+ * APIs](https://github.com/googleapis/googleapis),
37
+ * [Cloud Endpoints](https://cloud.google.com/endpoints), [gRPC
38
+ * Gateway](https://github.com/grpc-ecosystem/grpc-gateway),
39
+ * and [Envoy](https://github.com/envoyproxy/envoy) proxy support this feature
40
+ * and use it for large scale production services.
41
+ *
42
+ * `HttpRule` defines the schema of the gRPC/REST mapping. The mapping specifies
43
+ * how different portions of the gRPC request message are mapped to the URL
44
+ * path, URL query parameters, and HTTP request body. It also controls how the
45
+ * gRPC response message is mapped to the HTTP response body. `HttpRule` is
46
+ * typically specified as an `google.api.http` annotation on the gRPC method.
47
+ *
48
+ * Each mapping specifies a URL path template and an HTTP method. The path
49
+ * template may refer to one or more fields in the gRPC request message, as long
50
+ * as each field is a non-repeated field with a primitive (non-message) type.
51
+ * The path template controls how fields of the request message are mapped to
52
+ * the URL path.
53
+ *
54
+ * Example:
55
+ *
56
+ * service Messaging {
57
+ * rpc GetMessage(GetMessageRequest) returns (Message) {
58
+ * option (google.api.http) = {
59
+ * get: "/v1/{name=messages/*}"
60
+ * };
61
+ * }
62
+ * }
63
+ * message GetMessageRequest {
64
+ * string name = 1; // Mapped to URL path.
65
+ * }
66
+ * message Message {
67
+ * string text = 1; // The resource content.
68
+ * }
69
+ *
70
+ * This enables an HTTP REST to gRPC mapping as below:
71
+ *
72
+ * HTTP | gRPC
73
+ * -----|-----
74
+ * `GET /v1/messages/123456` | `GetMessage(name: "messages/123456")`
75
+ *
76
+ * Any fields in the request message which are not bound by the path template
77
+ * automatically become HTTP query parameters if there is no HTTP request body.
78
+ * For example:
79
+ *
80
+ * service Messaging {
81
+ * rpc GetMessage(GetMessageRequest) returns (Message) {
82
+ * option (google.api.http) = {
83
+ * get:"/v1/messages/{message_id}"
84
+ * };
85
+ * }
86
+ * }
87
+ * message GetMessageRequest {
88
+ * message SubMessage {
89
+ * string subfield = 1;
90
+ * }
91
+ * string message_id = 1; // Mapped to URL path.
92
+ * int64 revision = 2; // Mapped to URL query parameter `revision`.
93
+ * SubMessage sub = 3; // Mapped to URL query parameter `sub.subfield`.
94
+ * }
95
+ *
96
+ * This enables a HTTP JSON to RPC mapping as below:
97
+ *
98
+ * HTTP | gRPC
99
+ * -----|-----
100
+ * `GET /v1/messages/123456?revision=2&sub.subfield=foo` |
101
+ * `GetMessage(message_id: "123456" revision: 2 sub: SubMessage(subfield:
102
+ * "foo"))`
103
+ *
104
+ * Note that fields which are mapped to URL query parameters must have a
105
+ * primitive type or a repeated primitive type or a non-repeated message type.
106
+ * In the case of a repeated type, the parameter can be repeated in the URL
107
+ * as `...?param=A&param=B`. In the case of a message type, each field of the
108
+ * message is mapped to a separate parameter, such as
109
+ * `...?foo.a=A&foo.b=B&foo.c=C`.
110
+ *
111
+ * For HTTP methods that allow a request body, the `body` field
112
+ * specifies the mapping. Consider a REST update method on the
113
+ * message resource collection:
114
+ *
115
+ * service Messaging {
116
+ * rpc UpdateMessage(UpdateMessageRequest) returns (Message) {
117
+ * option (google.api.http) = {
118
+ * patch: "/v1/messages/{message_id}"
119
+ * body: "message"
120
+ * };
121
+ * }
122
+ * }
123
+ * message UpdateMessageRequest {
124
+ * string message_id = 1; // mapped to the URL
125
+ * Message message = 2; // mapped to the body
126
+ * }
127
+ *
128
+ * The following HTTP JSON to RPC mapping is enabled, where the
129
+ * representation of the JSON in the request body is determined by
130
+ * protos JSON encoding:
131
+ *
132
+ * HTTP | gRPC
133
+ * -----|-----
134
+ * `PATCH /v1/messages/123456 { "text": "Hi!" }` | `UpdateMessage(message_id:
135
+ * "123456" message { text: "Hi!" })`
136
+ *
137
+ * The special name `*` can be used in the body mapping to define that
138
+ * every field not bound by the path template should be mapped to the
139
+ * request body. This enables the following alternative definition of
140
+ * the update method:
141
+ *
142
+ * service Messaging {
143
+ * rpc UpdateMessage(Message) returns (Message) {
144
+ * option (google.api.http) = {
145
+ * patch: "/v1/messages/{message_id}"
146
+ * body: "*"
147
+ * };
148
+ * }
149
+ * }
150
+ * message Message {
151
+ * string message_id = 1;
152
+ * string text = 2;
153
+ * }
154
+ *
155
+ *
156
+ * The following HTTP JSON to RPC mapping is enabled:
157
+ *
158
+ * HTTP | gRPC
159
+ * -----|-----
160
+ * `PATCH /v1/messages/123456 { "text": "Hi!" }` | `UpdateMessage(message_id:
161
+ * "123456" text: "Hi!")`
162
+ *
163
+ * Note that when using `*` in the body mapping, it is not possible to
164
+ * have HTTP parameters, as all fields not bound by the path end in
165
+ * the body. This makes this option more rarely used in practice when
166
+ * defining REST APIs. The common usage of `*` is in custom methods
167
+ * which don't use the URL at all for transferring data.
168
+ *
169
+ * It is possible to define multiple HTTP methods for one RPC by using
170
+ * the `additional_bindings` option. Example:
171
+ *
172
+ * service Messaging {
173
+ * rpc GetMessage(GetMessageRequest) returns (Message) {
174
+ * option (google.api.http) = {
175
+ * get: "/v1/messages/{message_id}"
176
+ * additional_bindings {
177
+ * get: "/v1/users/{user_id}/messages/{message_id}"
178
+ * }
179
+ * };
180
+ * }
181
+ * }
182
+ * message GetMessageRequest {
183
+ * string message_id = 1;
184
+ * string user_id = 2;
185
+ * }
186
+ *
187
+ * This enables the following two alternative HTTP JSON to RPC mappings:
188
+ *
189
+ * HTTP | gRPC
190
+ * -----|-----
191
+ * `GET /v1/messages/123456` | `GetMessage(message_id: "123456")`
192
+ * `GET /v1/users/me/messages/123456` | `GetMessage(user_id: "me" message_id:
193
+ * "123456")`
194
+ *
195
+ * ## Rules for HTTP mapping
196
+ *
197
+ * 1. Leaf request fields (recursive expansion nested messages in the request
198
+ * message) are classified into three categories:
199
+ * - Fields referred by the path template. They are passed via the URL path.
200
+ * - Fields referred by the [HttpRule.body][google.api.HttpRule.body]. They are passed via the HTTP
201
+ * request body.
202
+ * - All other fields are passed via the URL query parameters, and the
203
+ * parameter name is the field path in the request message. A repeated
204
+ * field can be represented as multiple query parameters under the same
205
+ * name.
206
+ * 2. If [HttpRule.body][google.api.HttpRule.body] is "*", there is no URL query parameter, all fields
207
+ * are passed via URL path and HTTP request body.
208
+ * 3. If [HttpRule.body][google.api.HttpRule.body] is omitted, there is no HTTP request body, all
209
+ * fields are passed via URL path and URL query parameters.
210
+ *
211
+ * ### Path template syntax
212
+ *
213
+ * Template = "/" Segments [ Verb ] ;
214
+ * Segments = Segment { "/" Segment } ;
215
+ * Segment = "*" | "**" | LITERAL | Variable ;
216
+ * Variable = "{" FieldPath [ "=" Segments ] "}" ;
217
+ * FieldPath = IDENT { "." IDENT } ;
218
+ * Verb = ":" LITERAL ;
219
+ *
220
+ * The syntax `*` matches a single URL path segment. The syntax `**` matches
221
+ * zero or more URL path segments, which must be the last part of the URL path
222
+ * except the `Verb`.
223
+ *
224
+ * The syntax `Variable` matches part of the URL path as specified by its
225
+ * template. A variable template must not contain other variables. If a variable
226
+ * matches a single path segment, its template may be omitted, e.g. `{var}`
227
+ * is equivalent to `{var=*}`.
228
+ *
229
+ * The syntax `LITERAL` matches literal text in the URL path. If the `LITERAL`
230
+ * contains any reserved character, such characters should be percent-encoded
231
+ * before the matching.
232
+ *
233
+ * If a variable contains exactly one path segment, such as `"{var}"` or
234
+ * `"{var=*}"`, when such a variable is expanded into a URL path on the client
235
+ * side, all characters except `[-_.~0-9a-zA-Z]` are percent-encoded. The
236
+ * server side does the reverse decoding. Such variables show up in the
237
+ * [Discovery
238
+ * Document](https://developers.google.com/discovery/v1/reference/apis) as
239
+ * `{var}`.
240
+ *
241
+ * If a variable contains multiple path segments, such as `"{var=foo/*}"`
242
+ * or `"{var=**}"`, when such a variable is expanded into a URL path on the
243
+ * client side, all characters except `[-_.~/0-9a-zA-Z]` are percent-encoded.
244
+ * The server side does the reverse decoding, except "%2F" and "%2f" are left
245
+ * unchanged. Such variables show up in the
246
+ * [Discovery
247
+ * Document](https://developers.google.com/discovery/v1/reference/apis) as
248
+ * `{+var}`.
249
+ *
250
+ * ## Using gRPC API Service Configuration
251
+ *
252
+ * gRPC API Service Configuration (service config) is a configuration language
253
+ * for configuring a gRPC service to become a user-facing product. The
254
+ * service config is simply the YAML representation of the `google.api.Service`
255
+ * proto message.
256
+ *
257
+ * As an alternative to annotating your proto file, you can configure gRPC
258
+ * transcoding in your service config YAML files. You do this by specifying a
259
+ * `HttpRule` that maps the gRPC method to a REST endpoint, achieving the same
260
+ * effect as the proto annotation. This can be particularly useful if you
261
+ * have a proto that is reused in multiple services. Note that any transcoding
262
+ * specified in the service config will override any matching transcoding
263
+ * configuration in the proto.
264
+ *
265
+ * Example:
266
+ *
267
+ * http:
268
+ * rules:
269
+ * # Selects a gRPC method and applies HttpRule to it.
270
+ * - selector: example.v1.Messaging.GetMessage
271
+ * get: /v1/messages/{message_id}/{sub.subfield}
272
+ *
273
+ * ## Special notes
274
+ *
275
+ * When gRPC Transcoding is used to map a gRPC to JSON REST endpoints, the
276
+ * proto to JSON conversion must follow the [proto3
277
+ * specification](https://developers.google.com/protocol-buffers/docs/proto3#json).
278
+ *
279
+ * While the single segment variable follows the semantics of
280
+ * [RFC 6570](https://tools.ietf.org/html/rfc6570) Section 3.2.2 Simple String
281
+ * Expansion, the multi segment variable **does not** follow RFC 6570 Section
282
+ * 3.2.3 Reserved Expansion. The reason is that the Reserved Expansion
283
+ * does not expand special characters like `?` and `#`, which would lead
284
+ * to invalid URLs. As the result, gRPC Transcoding uses a custom encoding
285
+ * for multi segment variables.
286
+ *
287
+ * The path variables **must not** refer to any repeated or mapped field,
288
+ * because client libraries are not capable of handling such variable expansion.
289
+ *
290
+ * The path variables **must not** capture the leading "/" character. The reason
291
+ * is that the most common use case "{var}" does not capture the leading "/"
292
+ * character. For consistency, all path variables must share the same behavior.
293
+ *
294
+ * Repeated message fields must not be mapped to URL query parameters, because
295
+ * no client library can support such complicated mapping.
296
+ *
297
+ * If an API needs to use a JSON array for request or response body, it can map
298
+ * the request or response body to a repeated field. However, some gRPC
299
+ * Transcoding implementations may not support this feature.
300
+ *
301
+ * @generated from protobuf message google.api.HttpRule
302
+ */
303
+ export interface HttpRule {
304
+ /**
305
+ * Selects a method to which this rule applies.
306
+ *
307
+ * Refer to [selector][google.api.DocumentationRule.selector] for syntax details.
308
+ *
309
+ * @generated from protobuf field: string selector = 1;
310
+ */
311
+ selector: string;
312
+ /**
313
+ * @generated from protobuf oneof: pattern
314
+ */
315
+ pattern: {
316
+ oneofKind: "get";
317
+ /**
318
+ * Maps to HTTP GET. Used for listing and getting information about
319
+ * resources.
320
+ *
321
+ * @generated from protobuf field: string get = 2;
322
+ */
323
+ get: string;
324
+ } | {
325
+ oneofKind: "put";
326
+ /**
327
+ * Maps to HTTP PUT. Used for replacing a resource.
328
+ *
329
+ * @generated from protobuf field: string put = 3;
330
+ */
331
+ put: string;
332
+ } | {
333
+ oneofKind: "post";
334
+ /**
335
+ * Maps to HTTP POST. Used for creating a resource or performing an action.
336
+ *
337
+ * @generated from protobuf field: string post = 4;
338
+ */
339
+ post: string;
340
+ } | {
341
+ oneofKind: "delete";
342
+ /**
343
+ * Maps to HTTP DELETE. Used for deleting a resource.
344
+ *
345
+ * @generated from protobuf field: string delete = 5;
346
+ */
347
+ delete: string;
348
+ } | {
349
+ oneofKind: "patch";
350
+ /**
351
+ * Maps to HTTP PATCH. Used for updating a resource.
352
+ *
353
+ * @generated from protobuf field: string patch = 6;
354
+ */
355
+ patch: string;
356
+ } | {
357
+ oneofKind: "custom";
358
+ /**
359
+ * The custom pattern is used for specifying an HTTP method that is not
360
+ * included in the `pattern` field, such as HEAD, or "*" to leave the
361
+ * HTTP method unspecified for this rule. The wild-card rule is useful
362
+ * for services that provide content to Web (HTML) clients.
363
+ *
364
+ * @generated from protobuf field: google.api.CustomHttpPattern custom = 8;
365
+ */
366
+ custom: CustomHttpPattern;
367
+ } | {
368
+ oneofKind: undefined;
369
+ };
370
+ /**
371
+ * The name of the request field whose value is mapped to the HTTP request
372
+ * body, or `*` for mapping all request fields not captured by the path
373
+ * pattern to the HTTP body, or omitted for not having any HTTP request body.
374
+ *
375
+ * NOTE: the referred field must be present at the top-level of the request
376
+ * message type.
377
+ *
378
+ * @generated from protobuf field: string body = 7;
379
+ */
380
+ body: string;
381
+ /**
382
+ * Optional. The name of the response field whose value is mapped to the HTTP
383
+ * response body. When omitted, the entire response message will be used
384
+ * as the HTTP response body.
385
+ *
386
+ * NOTE: The referred field must be present at the top-level of the response
387
+ * message type.
388
+ *
389
+ * @generated from protobuf field: string response_body = 12;
390
+ */
391
+ responseBody: string;
392
+ /**
393
+ * Additional HTTP bindings for the selector. Nested bindings must
394
+ * not contain an `additional_bindings` field themselves (that is,
395
+ * the nesting may only be one level deep).
396
+ *
397
+ * @generated from protobuf field: repeated google.api.HttpRule additional_bindings = 11;
398
+ */
399
+ additionalBindings: HttpRule[];
400
+ }
401
+ /**
402
+ * A custom pattern is used for defining custom HTTP verb.
403
+ *
404
+ * @generated from protobuf message google.api.CustomHttpPattern
405
+ */
406
+ export interface CustomHttpPattern {
407
+ /**
408
+ * The name of this custom HTTP verb.
409
+ *
410
+ * @generated from protobuf field: string kind = 1;
411
+ */
412
+ kind: string;
413
+ /**
414
+ * The path matched by this custom verb.
415
+ *
416
+ * @generated from protobuf field: string path = 2;
417
+ */
418
+ path: string;
419
+ }
420
+ declare class Http$Type extends MessageType<Http> {
421
+ constructor();
422
+ create(value?: PartialMessage<Http>): Http;
423
+ internalBinaryRead(reader: IBinaryReader, length: number, options: BinaryReadOptions, target?: Http): Http;
424
+ internalBinaryWrite(message: Http, writer: IBinaryWriter, options: BinaryWriteOptions): IBinaryWriter;
425
+ }
426
+ /**
427
+ * @generated MessageType for protobuf message google.api.Http
428
+ */
429
+ export declare const Http: Http$Type;
430
+ declare class HttpRule$Type extends MessageType<HttpRule> {
431
+ constructor();
432
+ create(value?: PartialMessage<HttpRule>): HttpRule;
433
+ internalBinaryRead(reader: IBinaryReader, length: number, options: BinaryReadOptions, target?: HttpRule): HttpRule;
434
+ internalBinaryWrite(message: HttpRule, writer: IBinaryWriter, options: BinaryWriteOptions): IBinaryWriter;
435
+ }
436
+ /**
437
+ * @generated MessageType for protobuf message google.api.HttpRule
438
+ */
439
+ export declare const HttpRule: HttpRule$Type;
440
+ declare class CustomHttpPattern$Type extends MessageType<CustomHttpPattern> {
441
+ constructor();
442
+ create(value?: PartialMessage<CustomHttpPattern>): CustomHttpPattern;
443
+ internalBinaryRead(reader: IBinaryReader, length: number, options: BinaryReadOptions, target?: CustomHttpPattern): CustomHttpPattern;
444
+ internalBinaryWrite(message: CustomHttpPattern, writer: IBinaryWriter, options: BinaryWriteOptions): IBinaryWriter;
445
+ }
446
+ /**
447
+ * @generated MessageType for protobuf message google.api.CustomHttpPattern
448
+ */
449
+ export declare const CustomHttpPattern: CustomHttpPattern$Type;
450
+ export {};
451
+ //# sourceMappingURL=http.d.ts.map
@@ -0,0 +1 @@
1
+ {"version":3,"file":"http.d.ts","sourceRoot":"","sources":["../../../../src/proto/google/api/http.ts"],"names":[],"mappings":"AAkBA,OAAO,KAAK,EAAE,kBAAkB,EAAE,MAAM,sBAAsB,CAAC;AAC/D,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,sBAAsB,CAAC;AAE1D,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,sBAAsB,CAAC;AAC9D,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,sBAAsB,CAAC;AAE1D,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,sBAAsB,CAAC;AAE3D,OAAO,EAAE,WAAW,EAAE,MAAM,sBAAsB,CAAC;AACnD;;;;;;GAMG;AACH,MAAM,WAAW,IAAI;IACjB;;;;;;OAMG;IACH,KAAK,EAAE,QAAQ,EAAE,CAAC;IAClB;;;;;;;;;OASG;IACH,4BAA4B,EAAE,OAAO,CAAC;CACzC;AACD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgRG;AACH,MAAM,WAAW,QAAQ;IACrB;;;;;;OAMG;IACH,QAAQ,EAAE,MAAM,CAAC;IACjB;;OAEG;IACH,OAAO,EAAE;QACL,SAAS,EAAE,KAAK,CAAC;QACjB;;;;;WAKG;QACH,GAAG,EAAE,MAAM,CAAC;KACf,GAAG;QACA,SAAS,EAAE,KAAK,CAAC;QACjB;;;;WAIG;QACH,GAAG,EAAE,MAAM,CAAC;KACf,GAAG;QACA,SAAS,EAAE,MAAM,CAAC;QAClB;;;;WAIG;QACH,IAAI,EAAE,MAAM,CAAC;KAChB,GAAG;QACA,SAAS,EAAE,QAAQ,CAAC;QACpB;;;;WAIG;QACH,MAAM,EAAE,MAAM,CAAC;KAClB,GAAG;QACA,SAAS,EAAE,OAAO,CAAC;QACnB;;;;WAIG;QACH,KAAK,EAAE,MAAM,CAAC;KACjB,GAAG;QACA,SAAS,EAAE,QAAQ,CAAC;QACpB;;;;;;;WAOG;QACH,MAAM,EAAE,iBAAiB,CAAC;KAC7B,GAAG;QACA,SAAS,EAAE,SAAS,CAAC;KACxB,CAAC;IACF;;;;;;;;;OASG;IACH,IAAI,EAAE,MAAM,CAAC;IACb;;;;;;;;;OASG;IACH,YAAY,EAAE,MAAM,CAAC;IACrB;;;;;;OAMG;IACH,kBAAkB,EAAE,QAAQ,EAAE,CAAC;CAClC;AACD;;;;GAIG;AACH,MAAM,WAAW,iBAAiB;IAC9B;;;;OAIG;IACH,IAAI,EAAE,MAAM,CAAC;IACb;;;;OAIG;IACH,IAAI,EAAE,MAAM,CAAC;CAChB;AAED,cAAM,SAAU,SAAQ,WAAW,CAAC,IAAI,CAAC;;IAOrC,MAAM,CAAC,KAAK,CAAC,EAAE,cAAc,CAAC,IAAI,CAAC,GAAG,IAAI;IAQ1C,kBAAkB,CAAC,MAAM,EAAE,aAAa,EAAE,MAAM,EAAE,MAAM,EAAE,OAAO,EAAE,iBAAiB,EAAE,MAAM,CAAC,EAAE,IAAI,GAAG,IAAI;IAsB1G,mBAAmB,CAAC,OAAO,EAAE,IAAI,EAAE,MAAM,EAAE,aAAa,EAAE,OAAO,EAAE,kBAAkB,GAAG,aAAa;CAYxG;AACD;;GAEG;AACH,eAAO,MAAM,IAAI,WAAkB,CAAC;AAEpC,cAAM,aAAc,SAAQ,WAAW,CAAC,QAAQ,CAAC;;IAe7C,MAAM,CAAC,KAAK,CAAC,EAAE,cAAc,CAAC,QAAQ,CAAC,GAAG,QAAQ;IAWlD,kBAAkB,CAAC,MAAM,EAAE,aAAa,EAAE,MAAM,EAAE,MAAM,EAAE,OAAO,EAAE,iBAAiB,EAAE,MAAM,CAAC,EAAE,QAAQ,GAAG,QAAQ;IAgElH,mBAAmB,CAAC,OAAO,EAAE,QAAQ,EAAE,MAAM,EAAE,aAAa,EAAE,OAAO,EAAE,kBAAkB,GAAG,aAAa;CAoC5G;AACD;;GAEG;AACH,eAAO,MAAM,QAAQ,eAAsB,CAAC;AAE5C,cAAM,sBAAuB,SAAQ,WAAW,CAAC,iBAAiB,CAAC;;IAO/D,MAAM,CAAC,KAAK,CAAC,EAAE,cAAc,CAAC,iBAAiB,CAAC,GAAG,iBAAiB;IAQpE,kBAAkB,CAAC,MAAM,EAAE,aAAa,EAAE,MAAM,EAAE,MAAM,EAAE,OAAO,EAAE,iBAAiB,EAAE,MAAM,CAAC,EAAE,iBAAiB,GAAG,iBAAiB;IAsBpI,mBAAmB,CAAC,OAAO,EAAE,iBAAiB,EAAE,MAAM,EAAE,aAAa,EAAE,OAAO,EAAE,kBAAkB,GAAG,aAAa;CAYrH;AACD;;GAEG;AACH,eAAO,MAAM,iBAAiB,wBAA+B,CAAC"}
@@ -0,0 +1,172 @@
1
+ import { BinaryWriteOptions, IBinaryWriter, IBinaryReader, PartialMessage, JsonValue, JsonReadOptions, JsonWriteOptions, BinaryReadOptions, IMessageType, MessageType } from '@protobuf-ts/runtime';
2
+ /**
3
+ * `Any` contains an arbitrary serialized protocol buffer message along with a
4
+ * URL that describes the type of the serialized message.
5
+ *
6
+ * Protobuf library provides support to pack/unpack Any values in the form
7
+ * of utility functions or additional generated methods of the Any type.
8
+ *
9
+ * Example 1: Pack and unpack a message in C++.
10
+ *
11
+ * Foo foo = ...;
12
+ * Any any;
13
+ * any.PackFrom(foo);
14
+ * ...
15
+ * if (any.UnpackTo(&foo)) {
16
+ * ...
17
+ * }
18
+ *
19
+ * Example 2: Pack and unpack a message in Java.
20
+ *
21
+ * Foo foo = ...;
22
+ * Any any = Any.pack(foo);
23
+ * ...
24
+ * if (any.is(Foo.class)) {
25
+ * foo = any.unpack(Foo.class);
26
+ * }
27
+ * // or ...
28
+ * if (any.isSameTypeAs(Foo.getDefaultInstance())) {
29
+ * foo = any.unpack(Foo.getDefaultInstance());
30
+ * }
31
+ *
32
+ * Example 3: Pack and unpack a message in Python.
33
+ *
34
+ * foo = Foo(...)
35
+ * any = Any()
36
+ * any.Pack(foo)
37
+ * ...
38
+ * if any.Is(Foo.DESCRIPTOR):
39
+ * any.Unpack(foo)
40
+ * ...
41
+ *
42
+ * Example 4: Pack and unpack a message in Go
43
+ *
44
+ * foo := &pb.Foo{...}
45
+ * any, err := anypb.New(foo)
46
+ * if err != nil {
47
+ * ...
48
+ * }
49
+ * ...
50
+ * foo := &pb.Foo{}
51
+ * if err := any.UnmarshalTo(foo); err != nil {
52
+ * ...
53
+ * }
54
+ *
55
+ * The pack methods provided by protobuf library will by default use
56
+ * 'type.googleapis.com/full.type.name' as the type URL and the unpack
57
+ * methods only use the fully qualified type name after the last '/'
58
+ * in the type URL, for example "foo.bar.com/x/y.z" will yield type
59
+ * name "y.z".
60
+ *
61
+ * JSON
62
+ * ====
63
+ * The JSON representation of an `Any` value uses the regular
64
+ * representation of the deserialized, embedded message, with an
65
+ * additional field `@type` which contains the type URL. Example:
66
+ *
67
+ * package google.profile;
68
+ * message Person {
69
+ * string first_name = 1;
70
+ * string last_name = 2;
71
+ * }
72
+ *
73
+ * {
74
+ * "@type": "type.googleapis.com/google.profile.Person",
75
+ * "firstName": <string>,
76
+ * "lastName": <string>
77
+ * }
78
+ *
79
+ * If the embedded message type is well-known and has a custom JSON
80
+ * representation, that representation will be embedded adding a field
81
+ * `value` which holds the custom JSON in addition to the `@type`
82
+ * field. Example (for message [google.protobuf.Duration][]):
83
+ *
84
+ * {
85
+ * "@type": "type.googleapis.com/google.protobuf.Duration",
86
+ * "value": "1.212s"
87
+ * }
88
+ *
89
+ *
90
+ * @generated from protobuf message google.protobuf.Any
91
+ */
92
+ export interface Any {
93
+ /**
94
+ * A URL/resource name that uniquely identifies the type of the serialized
95
+ * protocol buffer message. This string must contain at least
96
+ * one "/" character. The last segment of the URL's path must represent
97
+ * the fully qualified name of the type (as in
98
+ * `path/google.protobuf.Duration`). The name should be in a canonical form
99
+ * (e.g., leading "." is not accepted).
100
+ *
101
+ * In practice, teams usually precompile into the binary all types that they
102
+ * expect it to use in the context of Any. However, for URLs which use the
103
+ * scheme `http`, `https`, or no scheme, one can optionally set up a type
104
+ * server that maps type URLs to message definitions as follows:
105
+ *
106
+ * * If no scheme is provided, `https` is assumed.
107
+ * * An HTTP GET on the URL must yield a [google.protobuf.Type][]
108
+ * value in binary format, or produce an error.
109
+ * * Applications are allowed to cache lookup results based on the
110
+ * URL, or have them precompiled into a binary to avoid any
111
+ * lookup. Therefore, binary compatibility needs to be preserved
112
+ * on changes to types. (Use versioned type names to manage
113
+ * breaking changes.)
114
+ *
115
+ * Note: this functionality is not currently available in the official
116
+ * protobuf release, and it is not used for type URLs beginning with
117
+ * type.googleapis.com. As of May 2023, there are no widely used type server
118
+ * implementations and no plans to implement one.
119
+ *
120
+ * Schemes other than `http`, `https` (or the empty scheme) might be
121
+ * used with implementation specific semantics.
122
+ *
123
+ *
124
+ * @generated from protobuf field: string type_url = 1;
125
+ */
126
+ typeUrl: string;
127
+ /**
128
+ * Must be a valid serialized protocol buffer of the above specified type.
129
+ *
130
+ * @generated from protobuf field: bytes value = 2;
131
+ */
132
+ value: Uint8Array;
133
+ }
134
+ declare class Any$Type extends MessageType<Any> {
135
+ constructor();
136
+ /**
137
+ * Pack the message into a new `Any`.
138
+ *
139
+ * Uses 'type.googleapis.com/full.type.name' as the type URL.
140
+ */
141
+ pack<T extends object>(message: T, type: IMessageType<T>): Any;
142
+ /**
143
+ * Unpack the message from the `Any`.
144
+ */
145
+ unpack<T extends object>(any: Any, type: IMessageType<T>, options?: Partial<BinaryReadOptions>): T;
146
+ /**
147
+ * Does the given `Any` contain a packed message of the given type?
148
+ */
149
+ contains(any: Any, type: IMessageType<any> | string): boolean;
150
+ /**
151
+ * Convert the message to canonical JSON value.
152
+ *
153
+ * You have to provide the `typeRegistry` option so that the
154
+ * packed message can be converted to JSON.
155
+ *
156
+ * The `typeRegistry` option is also required to read
157
+ * `google.protobuf.Any` from JSON format.
158
+ */
159
+ internalJsonWrite(any: Any, options: JsonWriteOptions): JsonValue;
160
+ internalJsonRead(json: JsonValue, options: JsonReadOptions, target?: Any): Any;
161
+ typeNameToUrl(name: string): string;
162
+ typeUrlToName(url: string): string;
163
+ create(value?: PartialMessage<Any>): Any;
164
+ internalBinaryRead(reader: IBinaryReader, length: number, options: BinaryReadOptions, target?: Any): Any;
165
+ internalBinaryWrite(message: Any, writer: IBinaryWriter, options: BinaryWriteOptions): IBinaryWriter;
166
+ }
167
+ /**
168
+ * @generated MessageType for protobuf message google.protobuf.Any
169
+ */
170
+ export declare const Any: Any$Type;
171
+ export {};
172
+ //# sourceMappingURL=any.d.ts.map
@@ -0,0 +1 @@
1
+ {"version":3,"file":"any.d.ts","sourceRoot":"","sources":["../../../../src/proto/google/protobuf/any.ts"],"names":[],"mappings":"AAkCA,OAAO,KAAK,EAAE,kBAAkB,EAAE,MAAM,sBAAsB,CAAC;AAC/D,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,sBAAsB,CAAC;AAE1D,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,sBAAsB,CAAC;AAE1D,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,sBAAsB,CAAC;AAI3D,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,sBAAsB,CAAC;AAEtD,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,sBAAsB,CAAC;AAC5D,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,sBAAsB,CAAC;AAC7D,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,sBAAsB,CAAC;AAC9D,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,sBAAsB,CAAC;AACzD,OAAO,EAAE,WAAW,EAAE,MAAM,sBAAsB,CAAC;AACnD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAyFG;AACH,MAAM,WAAW,GAAG;IAChB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OAgCG;IACH,OAAO,EAAE,MAAM,CAAC;IAChB;;;;OAIG;IACH,KAAK,EAAE,UAAU,CAAC;CACrB;AAED,cAAM,QAAS,SAAQ,WAAW,CAAC,GAAG,CAAC;;IAOnC;;;;OAIG;IACH,IAAI,CAAC,CAAC,SAAS,MAAM,EAAE,OAAO,EAAE,CAAC,EAAE,IAAI,EAAE,YAAY,CAAC,CAAC,CAAC,GAAG,GAAG;IAK9D;;OAEG;IACH,MAAM,CAAC,CAAC,SAAS,MAAM,EAAE,GAAG,EAAE,GAAG,EAAE,IAAI,EAAE,YAAY,CAAC,CAAC,CAAC,EAAE,OAAO,CAAC,EAAE,OAAO,CAAC,iBAAiB,CAAC,GAAG,CAAC;IAKlG;;OAEG;IACH,QAAQ,CAAC,GAAG,EAAE,GAAG,EAAE,IAAI,EAAE,YAAY,CAAC,GAAG,CAAC,GAAG,MAAM,GAAG,OAAO;IAO7D;;;;;;;;OAQG;IACH,iBAAiB,CAAC,GAAG,EAAE,GAAG,EAAE,OAAO,EAAE,gBAAgB,GAAG,SAAS;IAejE,gBAAgB,CAAC,IAAI,EAAE,SAAS,EAAE,OAAO,EAAE,eAAe,EAAE,MAAM,CAAC,EAAE,GAAG,GAAG,GAAG;IAuB9E,aAAa,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM;IAKnC,aAAa,CAAC,GAAG,EAAE,MAAM,GAAG,MAAM;IASlC,MAAM,CAAC,KAAK,CAAC,EAAE,cAAc,CAAC,GAAG,CAAC,GAAG,GAAG;IAQxC,kBAAkB,CAAC,MAAM,EAAE,aAAa,EAAE,MAAM,EAAE,MAAM,EAAE,OAAO,EAAE,iBAAiB,EAAE,MAAM,CAAC,EAAE,GAAG,GAAG,GAAG;IAsBxG,mBAAmB,CAAC,OAAO,EAAE,GAAG,EAAE,MAAM,EAAE,aAAa,EAAE,OAAO,EAAE,kBAAkB,GAAG,aAAa;CAYvG;AACD;;GAEG;AACH,eAAO,MAAM,GAAG,UAAiB,CAAC"}