@delopay/sdk 0.138.0 → 0.139.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.
- package/dist/internal.d.cts +16 -1
- package/dist/internal.d.ts +16 -1
- package/package.json +1 -1
package/dist/internal.d.cts
CHANGED
|
@@ -1295,6 +1295,12 @@ interface DiagnosticPaymentListParams extends DiagnosticListParamsBase {
|
|
|
1295
1295
|
connector?: string[];
|
|
1296
1296
|
status?: string[];
|
|
1297
1297
|
error_code?: string;
|
|
1298
|
+
/**
|
|
1299
|
+
* Any id pasted into the console, matched against the payment and its
|
|
1300
|
+
* attempt. Without it this tab ignored the pivot while the page drew a chip
|
|
1301
|
+
* saying the filter was applied.
|
|
1302
|
+
*/
|
|
1303
|
+
object_id?: string;
|
|
1298
1304
|
/** Non-terminal for at least this long. Omit to show failures alone. */
|
|
1299
1305
|
stuck_minutes?: number;
|
|
1300
1306
|
}
|
|
@@ -1372,7 +1378,16 @@ interface DiagnosticOutgoingWebhook {
|
|
|
1372
1378
|
/** One entry per attempt, oldest first — the row of squares the page draws. */
|
|
1373
1379
|
attempts: DiagnosticOutgoingAttempt[];
|
|
1374
1380
|
delivered: boolean | null;
|
|
1375
|
-
|
|
1381
|
+
/**
|
|
1382
|
+
* Why the chain stopped, when it did — `null` while it is still retrying.
|
|
1383
|
+
*
|
|
1384
|
+
* Named `terminal_reason` because that is what the router sends
|
|
1385
|
+
* (`OutgoingWebhookRow` in the OpenAPI spec). It was `delivery_terminal_reason`
|
|
1386
|
+
* here, which typechecks against nothing and reads `undefined` at runtime, so
|
|
1387
|
+
* every undelivered row looked like one still inside its retry budget and the
|
|
1388
|
+
* "endpoint rejected" state was unreachable.
|
|
1389
|
+
*/
|
|
1390
|
+
terminal_reason: string | null;
|
|
1376
1391
|
test_mode: boolean | null;
|
|
1377
1392
|
}
|
|
1378
1393
|
interface DiagnosticOutgoingWebhookSummary {
|
package/dist/internal.d.ts
CHANGED
|
@@ -1295,6 +1295,12 @@ interface DiagnosticPaymentListParams extends DiagnosticListParamsBase {
|
|
|
1295
1295
|
connector?: string[];
|
|
1296
1296
|
status?: string[];
|
|
1297
1297
|
error_code?: string;
|
|
1298
|
+
/**
|
|
1299
|
+
* Any id pasted into the console, matched against the payment and its
|
|
1300
|
+
* attempt. Without it this tab ignored the pivot while the page drew a chip
|
|
1301
|
+
* saying the filter was applied.
|
|
1302
|
+
*/
|
|
1303
|
+
object_id?: string;
|
|
1298
1304
|
/** Non-terminal for at least this long. Omit to show failures alone. */
|
|
1299
1305
|
stuck_minutes?: number;
|
|
1300
1306
|
}
|
|
@@ -1372,7 +1378,16 @@ interface DiagnosticOutgoingWebhook {
|
|
|
1372
1378
|
/** One entry per attempt, oldest first — the row of squares the page draws. */
|
|
1373
1379
|
attempts: DiagnosticOutgoingAttempt[];
|
|
1374
1380
|
delivered: boolean | null;
|
|
1375
|
-
|
|
1381
|
+
/**
|
|
1382
|
+
* Why the chain stopped, when it did — `null` while it is still retrying.
|
|
1383
|
+
*
|
|
1384
|
+
* Named `terminal_reason` because that is what the router sends
|
|
1385
|
+
* (`OutgoingWebhookRow` in the OpenAPI spec). It was `delivery_terminal_reason`
|
|
1386
|
+
* here, which typechecks against nothing and reads `undefined` at runtime, so
|
|
1387
|
+
* every undelivered row looked like one still inside its retry budget and the
|
|
1388
|
+
* "endpoint rejected" state was unreachable.
|
|
1389
|
+
*/
|
|
1390
|
+
terminal_reason: string | null;
|
|
1376
1391
|
test_mode: boolean | null;
|
|
1377
1392
|
}
|
|
1378
1393
|
interface DiagnosticOutgoingWebhookSummary {
|