@leaflow/sdk 0.0.0-dev.129.g409f04f → 0.0.0-dev.130.g2ad4b23

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.
@@ -312,13 +312,11 @@ export interface components {
312
312
  Error: {
313
313
  code?: string;
314
314
  message: string;
315
+ /**
316
+ * @description What a given `code` carries alongside the message. The keys depend on the code,
317
+ * and a client that does not recognise one ignores it.
318
+ */
315
319
  meta?: {
316
- /**
317
- * @description Present on every response whose `code` is `VALIDATION_FAILED`, and on no
318
- * other response.
319
- */
320
- violations?: components["schemas"]["Violation"][];
321
- } & {
322
320
  [key: string]: unknown;
323
321
  };
324
322
  /** Format: int64 */
@@ -605,29 +603,6 @@ export interface components {
605
603
  /** @description Always `Bearer` */
606
604
  token_type: string;
607
605
  };
608
- /**
609
- * @description A single mismatch between the request and the contract.
610
- *
611
- * Use `field` to locate the input, `rule` to decide what to tell the user, and
612
- * `reason` only for diagnostics.
613
- */
614
- Violation: {
615
- /**
616
- * @description Dot-separated path to the field, such as `name` or
617
- * `schedule.0.start_time_seconds`.
618
- */
619
- field: string;
620
- /**
621
- * @description The JSON Schema keyword that failed, such as `minLength`, `minimum` or
622
- * `pattern`.
623
- */
624
- rule: string;
625
- /**
626
- * @description The validator's own wording, in English. Intended for diagnostics; do not
627
- * display it to end users.
628
- */
629
- reason?: string;
630
- };
631
606
  };
632
607
  responses: never;
633
608
  parameters: never;
@@ -679,13 +679,11 @@ export interface components {
679
679
  Error: {
680
680
  code?: string;
681
681
  message: string;
682
+ /**
683
+ * @description What a given `code` carries alongside the message. The keys depend on the code,
684
+ * and a client that does not recognise one ignores it.
685
+ */
682
686
  meta?: {
683
- /**
684
- * @description Present on every response whose `code` is `VALIDATION_FAILED`, and on no
685
- * other response.
686
- */
687
- violations?: components["schemas"]["Violation"][];
688
- } & {
689
687
  [key: string]: unknown;
690
688
  };
691
689
  /** Format: int64 */
@@ -1429,29 +1427,6 @@ export interface components {
1429
1427
  UpdateFolderRequestBody: {
1430
1428
  name: string;
1431
1429
  };
1432
- /**
1433
- * @description A single mismatch between the request and the contract.
1434
- *
1435
- * Use `field` to locate the input, `rule` to decide what to tell the user, and
1436
- * `reason` only for diagnostics.
1437
- */
1438
- Violation: {
1439
- /**
1440
- * @description Dot-separated path to the field, such as `name` or
1441
- * `schedule.0.start_time_seconds`.
1442
- */
1443
- field: string;
1444
- /**
1445
- * @description The JSON Schema keyword that failed, such as `minLength`, `minimum` or
1446
- * `pattern`.
1447
- */
1448
- rule: string;
1449
- /**
1450
- * @description The validator's own wording, in English. Intended for diagnostics; do not
1451
- * display it to end users.
1452
- */
1453
- reason?: string;
1454
- };
1455
1430
  };
1456
1431
  responses: never;
1457
1432
  parameters: never;
@@ -1299,13 +1299,11 @@ export interface components {
1299
1299
  Error: {
1300
1300
  code?: string;
1301
1301
  message: string;
1302
+ /**
1303
+ * @description What a given `code` carries alongside the message. The keys depend on the code,
1304
+ * and a client that does not recognise one ignores it.
1305
+ */
1302
1306
  meta?: {
1303
- /**
1304
- * @description Present on every response whose `code` is `VALIDATION_FAILED`, and on no
1305
- * other response.
1306
- */
1307
- violations?: components["schemas"]["Violation"][];
1308
- } & {
1309
1307
  [key: string]: unknown;
1310
1308
  };
1311
1309
  /** Format: int64 */
@@ -2815,29 +2813,6 @@ export interface components {
2815
2813
  /** Format: int64 */
2816
2814
  total_count?: number;
2817
2815
  };
2818
- /**
2819
- * @description A single mismatch between the request and the contract.
2820
- *
2821
- * Use `field` to locate the input, `rule` to decide what to tell the user, and
2822
- * `reason` only for diagnostics.
2823
- */
2824
- Violation: {
2825
- /**
2826
- * @description Dot-separated path to the field, such as `name` or
2827
- * `schedule.0.start_time_seconds`.
2828
- */
2829
- field: string;
2830
- /**
2831
- * @description The JSON Schema keyword that failed, such as `minLength`, `minimum` or
2832
- * `pattern`.
2833
- */
2834
- rule: string;
2835
- /**
2836
- * @description The validator's own wording, in English. Intended for diagnostics; do not
2837
- * display it to end users.
2838
- */
2839
- reason?: string;
2840
- };
2841
2816
  };
2842
2817
  responses: {
2843
2818
  /** @description Unchanged since the `ETag` that was sent. No body. */
@@ -286,13 +286,11 @@ export interface components {
286
286
  Error: {
287
287
  code?: string;
288
288
  message: string;
289
+ /**
290
+ * @description What a given `code` carries alongside the message. The keys depend on the code,
291
+ * and a client that does not recognise one ignores it.
292
+ */
289
293
  meta?: {
290
- /**
291
- * @description Present on every response whose `code` is `VALIDATION_FAILED`, and on no
292
- * other response.
293
- */
294
- violations?: components["schemas"]["Violation"][];
295
- } & {
296
294
  [key: string]: unknown;
297
295
  };
298
296
  /** Format: int64 */
@@ -569,29 +567,6 @@ export interface components {
569
567
  UsageTimelineResponseBody: {
570
568
  items: components["schemas"]["UsageBucketResource"][];
571
569
  };
572
- /**
573
- * @description A single mismatch between the request and the contract.
574
- *
575
- * Use `field` to locate the input, `rule` to decide what to tell the user, and
576
- * `reason` only for diagnostics.
577
- */
578
- Violation: {
579
- /**
580
- * @description Dot-separated path to the field, such as `name` or
581
- * `schedule.0.start_time_seconds`.
582
- */
583
- field: string;
584
- /**
585
- * @description The JSON Schema keyword that failed, such as `minLength`, `minimum` or
586
- * `pattern`.
587
- */
588
- rule: string;
589
- /**
590
- * @description The validator's own wording, in English. Intended for diagnostics; do not
591
- * display it to end users.
592
- */
593
- reason?: string;
594
- };
595
570
  };
596
571
  responses: never;
597
572
  parameters: never;
@@ -1310,13 +1310,11 @@ export interface components {
1310
1310
  Error: {
1311
1311
  code?: string;
1312
1312
  message: string;
1313
+ /**
1314
+ * @description What a given `code` carries alongside the message. The keys depend on the code,
1315
+ * and a client that does not recognise one ignores it.
1316
+ */
1313
1317
  meta?: {
1314
- /**
1315
- * @description Present on every response whose `code` is `VALIDATION_FAILED`, and on no
1316
- * other response.
1317
- */
1318
- violations?: components["schemas"]["Violation"][];
1319
- } & {
1320
1318
  [key: string]: unknown;
1321
1319
  };
1322
1320
  /** Format: int64 */
@@ -2439,29 +2437,6 @@ export interface components {
2439
2437
  RenameSnapshotRequestBody: {
2440
2438
  name: string;
2441
2439
  };
2442
- /**
2443
- * @description A single mismatch between the request and the contract.
2444
- *
2445
- * Use `field` to locate the input, `rule` to decide what to tell the user, and
2446
- * `reason` only for diagnostics.
2447
- */
2448
- Violation: {
2449
- /**
2450
- * @description Dot-separated path to the field, such as `name` or
2451
- * `schedule.0.start_time_seconds`.
2452
- */
2453
- field: string;
2454
- /**
2455
- * @description The JSON Schema keyword that failed, such as `minLength`, `minimum` or
2456
- * `pattern`.
2457
- */
2458
- rule: string;
2459
- /**
2460
- * @description The validator's own wording, in English. Intended for diagnostics; do not
2461
- * display it to end users.
2462
- */
2463
- reason?: string;
2464
- };
2465
2440
  };
2466
2441
  responses: never;
2467
2442
  parameters: never;
@@ -234,13 +234,11 @@ export interface components {
234
234
  Error: {
235
235
  code?: string;
236
236
  message: string;
237
+ /**
238
+ * @description What a given `code` carries alongside the message. The keys depend on the code,
239
+ * and a client that does not recognise one ignores it.
240
+ */
237
241
  meta?: {
238
- /**
239
- * @description Present on every response whose `code` is `VALIDATION_FAILED`, and on no
240
- * other response.
241
- */
242
- violations?: components["schemas"]["Violation"][];
243
- } & {
244
242
  [key: string]: unknown;
245
243
  };
246
244
  /** Format: int64 */
@@ -450,29 +448,6 @@ export interface components {
450
448
  */
451
449
  ttl?: number;
452
450
  };
453
- /**
454
- * @description A single mismatch between the request and the contract.
455
- *
456
- * Use `field` to locate the input, `rule` to decide what to tell the user, and
457
- * `reason` only for diagnostics.
458
- */
459
- Violation: {
460
- /**
461
- * @description Dot-separated path to the field, such as `name` or
462
- * `schedule.0.start_time_seconds`.
463
- */
464
- field: string;
465
- /**
466
- * @description The JSON Schema keyword that failed, such as `minLength`, `minimum` or
467
- * `pattern`.
468
- */
469
- rule: string;
470
- /**
471
- * @description The validator's own wording, in English. Intended for diagnostics; do not
472
- * display it to end users.
473
- */
474
- reason?: string;
475
- };
476
451
  };
477
452
  responses: never;
478
453
  parameters: never;
@@ -56,13 +56,11 @@ export interface components {
56
56
  Error: {
57
57
  code?: string;
58
58
  message: string;
59
+ /**
60
+ * @description What a given `code` carries alongside the message. The keys depend on the code,
61
+ * and a client that does not recognise one ignores it.
62
+ */
59
63
  meta?: {
60
- /**
61
- * @description Present on every response whose `code` is `VALIDATION_FAILED`, and on no
62
- * other response.
63
- */
64
- violations?: components["schemas"]["Violation"][];
65
- } & {
66
64
  [key: string]: unknown;
67
65
  };
68
66
  /** Format: int64 */
@@ -86,29 +84,6 @@ export interface components {
86
84
  AvailabilityZoneListResponseBody: {
87
85
  items: components["schemas"]["AvailabilityZoneResource"][] | null;
88
86
  };
89
- /**
90
- * @description A single mismatch between the request and the contract.
91
- *
92
- * Use `field` to locate the input, `rule` to decide what to tell the user, and
93
- * `reason` only for diagnostics.
94
- */
95
- Violation: {
96
- /**
97
- * @description Dot-separated path to the field, such as `name` or
98
- * `schedule.0.start_time_seconds`.
99
- */
100
- field: string;
101
- /**
102
- * @description The JSON Schema keyword that failed, such as `minLength`, `minimum` or
103
- * `pattern`.
104
- */
105
- rule: string;
106
- /**
107
- * @description The validator's own wording, in English. Intended for diagnostics; do not
108
- * display it to end users.
109
- */
110
- reason?: string;
111
- };
112
87
  };
113
88
  responses: never;
114
89
  parameters: never;
@@ -381,13 +381,11 @@ export interface components {
381
381
  Error: {
382
382
  code?: string;
383
383
  message: string;
384
+ /**
385
+ * @description What a given `code` carries alongside the message. The keys depend on the code,
386
+ * and a client that does not recognise one ignores it.
387
+ */
384
388
  meta?: {
385
- /**
386
- * @description Present on every response whose `code` is `VALIDATION_FAILED`, and on no
387
- * other response.
388
- */
389
- violations?: components["schemas"]["Violation"][];
390
- } & {
391
389
  [key: string]: unknown;
392
390
  };
393
391
  /** Format: int64 */
@@ -716,29 +714,6 @@ export interface components {
716
714
  RenameSSHKeyRequestBody: {
717
715
  name: string;
718
716
  };
719
- /**
720
- * @description A single mismatch between the request and the contract.
721
- *
722
- * Use `field` to locate the input, `rule` to decide what to tell the user, and
723
- * `reason` only for diagnostics.
724
- */
725
- Violation: {
726
- /**
727
- * @description Dot-separated path to the field, such as `name` or
728
- * `schedule.0.start_time_seconds`.
729
- */
730
- field: string;
731
- /**
732
- * @description The JSON Schema keyword that failed, such as `minLength`, `minimum` or
733
- * `pattern`.
734
- */
735
- rule: string;
736
- /**
737
- * @description The validator's own wording, in English. Intended for diagnostics; do not
738
- * display it to end users.
739
- */
740
- reason?: string;
741
- };
742
717
  };
743
718
  responses: never;
744
719
  parameters: never;
@@ -958,13 +958,11 @@ export interface components {
958
958
  Error: {
959
959
  code?: string;
960
960
  message: string;
961
+ /**
962
+ * @description What a given `code` carries alongside the message. The keys depend on the code,
963
+ * and a client that does not recognise one ignores it.
964
+ */
961
965
  meta?: {
962
- /**
963
- * @description Present on every response whose `code` is `VALIDATION_FAILED`, and on no
964
- * other response.
965
- */
966
- violations?: components["schemas"]["Violation"][];
967
- } & {
968
966
  [key: string]: unknown;
969
967
  };
970
968
  /** Format: int64 */
@@ -2036,29 +2034,6 @@ export interface components {
2036
2034
  /** @description Your own domain, such as status.acme.com. It must already point at the status page by CNAME */
2037
2035
  domain: string;
2038
2036
  };
2039
- /**
2040
- * @description A single mismatch between the request and the contract.
2041
- *
2042
- * Use `field` to locate the input, `rule` to decide what to tell the user, and
2043
- * `reason` only for diagnostics.
2044
- */
2045
- Violation: {
2046
- /**
2047
- * @description Dot-separated path to the field, such as `name` or
2048
- * `schedule.0.start_time_seconds`.
2049
- */
2050
- field: string;
2051
- /**
2052
- * @description The JSON Schema keyword that failed, such as `minLength`, `minimum` or
2053
- * `pattern`.
2054
- */
2055
- rule: string;
2056
- /**
2057
- * @description The validator's own wording, in English. Intended for diagnostics; do not
2058
- * display it to end users.
2059
- */
2060
- reason?: string;
2061
- };
2062
2037
  };
2063
2038
  responses: never;
2064
2039
  parameters: never;
@@ -624,13 +624,11 @@ export interface components {
624
624
  Error: {
625
625
  code?: string;
626
626
  message: string;
627
+ /**
628
+ * @description What a given `code` carries alongside the message. The keys depend on the code,
629
+ * and a client that does not recognise one ignores it.
630
+ */
627
631
  meta?: {
628
- /**
629
- * @description Present on every response whose `code` is `VALIDATION_FAILED`, and on no
630
- * other response.
631
- */
632
- violations?: components["schemas"]["Violation"][];
633
- } & {
634
632
  [key: string]: unknown;
635
633
  };
636
634
  /** Format: int64 */
@@ -1094,29 +1092,6 @@ export interface components {
1094
1092
  /** @description The authorization token for this subscription, passed back to the realtime server by the client library */
1095
1093
  auth: string;
1096
1094
  };
1097
- /**
1098
- * @description A single mismatch between the request and the contract.
1099
- *
1100
- * Use `field` to locate the input, `rule` to decide what to tell the user, and
1101
- * `reason` only for diagnostics.
1102
- */
1103
- Violation: {
1104
- /**
1105
- * @description Dot-separated path to the field, such as `name` or
1106
- * `schedule.0.start_time_seconds`.
1107
- */
1108
- field: string;
1109
- /**
1110
- * @description The JSON Schema keyword that failed, such as `minLength`, `minimum` or
1111
- * `pattern`.
1112
- */
1113
- rule: string;
1114
- /**
1115
- * @description The validator's own wording, in English. Intended for diagnostics; do not
1116
- * display it to end users.
1117
- */
1118
- reason?: string;
1119
- };
1120
1095
  };
1121
1096
  responses: never;
1122
1097
  parameters: {
@@ -298,13 +298,11 @@ export interface components {
298
298
  Error: {
299
299
  code?: string;
300
300
  message: string;
301
+ /**
302
+ * @description What a given `code` carries alongside the message. The keys depend on the code,
303
+ * and a client that does not recognise one ignores it.
304
+ */
301
305
  meta?: {
302
- /**
303
- * @description Present on every response whose `code` is `VALIDATION_FAILED`, and on no
304
- * other response.
305
- */
306
- violations?: components["schemas"]["Violation"][];
307
- } & {
308
306
  [key: string]: unknown;
309
307
  };
310
308
  /** Format: int64 */
@@ -558,29 +556,6 @@ export interface components {
558
556
  /** Format: int64 */
559
557
  total: number;
560
558
  };
561
- /**
562
- * @description A single mismatch between the request and the contract.
563
- *
564
- * Use `field` to locate the input, `rule` to decide what to tell the user, and
565
- * `reason` only for diagnostics.
566
- */
567
- Violation: {
568
- /**
569
- * @description Dot-separated path to the field, such as `name` or
570
- * `schedule.0.start_time_seconds`.
571
- */
572
- field: string;
573
- /**
574
- * @description The JSON Schema keyword that failed, such as `minLength`, `minimum` or
575
- * `pattern`.
576
- */
577
- rule: string;
578
- /**
579
- * @description The validator's own wording, in English. Intended for diagnostics; do not
580
- * display it to end users.
581
- */
582
- reason?: string;
583
- };
584
559
  };
585
560
  responses: never;
586
561
  parameters: never;
@@ -134,13 +134,11 @@ export interface components {
134
134
  Error: {
135
135
  code?: string;
136
136
  message: string;
137
+ /**
138
+ * @description What a given `code` carries alongside the message. The keys depend on the code,
139
+ * and a client that does not recognise one ignores it.
140
+ */
137
141
  meta?: {
138
- /**
139
- * @description Present on every response whose `code` is `VALIDATION_FAILED`, and on no
140
- * other response.
141
- */
142
- violations?: components["schemas"]["Violation"][];
143
- } & {
144
142
  [key: string]: unknown;
145
143
  };
146
144
  /** Format: int64 */
@@ -218,29 +216,6 @@ export interface components {
218
216
  days: number;
219
217
  points: components["schemas"]["UsageDayResource"][];
220
218
  };
221
- /**
222
- * @description A single mismatch between the request and the contract.
223
- *
224
- * Use `field` to locate the input, `rule` to decide what to tell the user, and
225
- * `reason` only for diagnostics.
226
- */
227
- Violation: {
228
- /**
229
- * @description Dot-separated path to the field, such as `name` or
230
- * `schedule.0.start_time_seconds`.
231
- */
232
- field: string;
233
- /**
234
- * @description The JSON Schema keyword that failed, such as `minLength`, `minimum` or
235
- * `pattern`.
236
- */
237
- rule: string;
238
- /**
239
- * @description The validator's own wording, in English. Intended for diagnostics; do not
240
- * display it to end users.
241
- */
242
- reason?: string;
243
- };
244
219
  };
245
220
  responses: never;
246
221
  parameters: never;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@leaflow/sdk",
3
- "version": "0.0.0-dev.129.g409f04f",
3
+ "version": "0.0.0-dev.130.g2ad4b23",
4
4
  "description": "Leaflow 平台 API 的 TypeScript SDK",
5
5
  "license": "MIT",
6
6
  "repository": {