@shipstatic/ship 3.4.0-beta.5 → 3.4.0-beta.6
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/THIRD-PARTY-LICENSES.md +1 -1
- package/dist/browser.d.ts +8 -34
- package/dist/browser.js.map +1 -1
- package/dist/cli.cjs.map +1 -1
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +8 -34
- package/dist/index.d.ts +8 -34
- package/dist/index.js.map +1 -1
- package/package.json +2 -2
package/dist/index.d.cts
CHANGED
|
@@ -942,12 +942,10 @@ interface Account {
|
|
|
942
942
|
* from where the account stands. It excludes the plan and cadence the
|
|
943
943
|
* account already holds and the one move the door refuses, a dearer tier
|
|
944
944
|
* at a shorter interval (an immediate move would mint a proration credit,
|
|
945
|
-
* a deferred one would make a customer asking for more wait a year).
|
|
946
|
-
*
|
|
947
|
-
*
|
|
948
|
-
*
|
|
949
|
-
* model instead of restating it. Additive: absent on responses that
|
|
950
|
-
* predate it, and a client then derives as it did.
|
|
945
|
+
* a deferred one would make a customer asking for more wait a year). The
|
|
946
|
+
* rule's owner is the platform's plan table; a console feeds these
|
|
947
|
+
* intervals into its own move model instead of restating it. Additive:
|
|
948
|
+
* absent on responses that predate it, and a client then derives as it did.
|
|
951
949
|
*/
|
|
952
950
|
readonly destinations?: PlanDestination[];
|
|
953
951
|
}
|
|
@@ -959,17 +957,6 @@ interface Account {
|
|
|
959
957
|
interface PlanDestination {
|
|
960
958
|
readonly plan: AccountPlanType;
|
|
961
959
|
readonly intervals: BillingInterval[];
|
|
962
|
-
/**
|
|
963
|
-
* What the account holds beyond what this plan allows: per kind, how many
|
|
964
|
-
* to remove. Present only on a cheaper tier the account does not fit, and
|
|
965
|
-
* then never empty. A move down a tier is booked only by an account that
|
|
966
|
-
* fits it, so the change door refuses the move until the owner has removed
|
|
967
|
-
* the excess, and the field is gone from the next read. A move already
|
|
968
|
-
* booked says the same of itself ({@link ScheduledChange.excess}). Which
|
|
969
|
-
* kinds count is the platform's to decide; a client renders the keys it is
|
|
970
|
-
* given.
|
|
971
|
-
*/
|
|
972
|
-
readonly excess?: Partial<Caps>;
|
|
973
960
|
}
|
|
974
961
|
/**
|
|
975
962
|
* Acknowledgement of `DELETE /account` (202). Termination is asynchronous —
|
|
@@ -2499,9 +2486,10 @@ interface PlansResponse {
|
|
|
2499
2486
|
* Schedule that applies the change at period end. The answer says which
|
|
2500
2487
|
* happened ({@link PlanChangeResponse}).
|
|
2501
2488
|
*
|
|
2502
|
-
* A move down a tier is
|
|
2503
|
-
*
|
|
2504
|
-
*
|
|
2489
|
+
* A move down a tier is booked only by an account that fits it: while the
|
|
2490
|
+
* account holds more members or domains than the destination allows, the
|
|
2491
|
+
* door refuses (400) with a sentence naming what to remove, and the same
|
|
2492
|
+
* counts in `details.excess`, keyed like {@link Caps}.
|
|
2505
2493
|
*/
|
|
2506
2494
|
interface PlanChangeRequest {
|
|
2507
2495
|
readonly plan: AccountPlanType;
|
|
@@ -2523,20 +2511,6 @@ interface ScheduledChange {
|
|
|
2523
2511
|
readonly plan: AccountPlanType;
|
|
2524
2512
|
readonly interval: BillingInterval;
|
|
2525
2513
|
readonly at: number;
|
|
2526
|
-
/**
|
|
2527
|
-
* What the account must remove before `at` to fit the booked plan: per
|
|
2528
|
-
* kind, how many, in {@link PlanDestination.excess}'s shape. A move down a
|
|
2529
|
-
* tier is booked by an account that fits it, so this is absent on the day
|
|
2530
|
-
* of booking and on the change door's answer. The account keeps its
|
|
2531
|
-
* current plan until the change applies, though, and may add a member or
|
|
2532
|
-
* a domain the booked plan has no room for; `GET /account` then counts
|
|
2533
|
-
* them here, for as long as the change is booked, whatever else the
|
|
2534
|
-
* account may or may not order meanwhile. It is a count to REMOVE, not of
|
|
2535
|
-
* what pauses: holdings that do not fit when the change applies are
|
|
2536
|
-
* paused by the platform's own rule, which for members pauses every
|
|
2537
|
-
* member while the account is over. Absent while the account fits.
|
|
2538
|
-
*/
|
|
2539
|
-
readonly excess?: Partial<Caps>;
|
|
2540
2514
|
}
|
|
2541
2515
|
/**
|
|
2542
2516
|
* The answer of `POST /billing/change` — exactly one field is set, and the
|
package/dist/index.d.ts
CHANGED
|
@@ -942,12 +942,10 @@ interface Account {
|
|
|
942
942
|
* from where the account stands. It excludes the plan and cadence the
|
|
943
943
|
* account already holds and the one move the door refuses, a dearer tier
|
|
944
944
|
* at a shorter interval (an immediate move would mint a proration credit,
|
|
945
|
-
* a deferred one would make a customer asking for more wait a year).
|
|
946
|
-
*
|
|
947
|
-
*
|
|
948
|
-
*
|
|
949
|
-
* model instead of restating it. Additive: absent on responses that
|
|
950
|
-
* predate it, and a client then derives as it did.
|
|
945
|
+
* a deferred one would make a customer asking for more wait a year). The
|
|
946
|
+
* rule's owner is the platform's plan table; a console feeds these
|
|
947
|
+
* intervals into its own move model instead of restating it. Additive:
|
|
948
|
+
* absent on responses that predate it, and a client then derives as it did.
|
|
951
949
|
*/
|
|
952
950
|
readonly destinations?: PlanDestination[];
|
|
953
951
|
}
|
|
@@ -959,17 +957,6 @@ interface Account {
|
|
|
959
957
|
interface PlanDestination {
|
|
960
958
|
readonly plan: AccountPlanType;
|
|
961
959
|
readonly intervals: BillingInterval[];
|
|
962
|
-
/**
|
|
963
|
-
* What the account holds beyond what this plan allows: per kind, how many
|
|
964
|
-
* to remove. Present only on a cheaper tier the account does not fit, and
|
|
965
|
-
* then never empty. A move down a tier is booked only by an account that
|
|
966
|
-
* fits it, so the change door refuses the move until the owner has removed
|
|
967
|
-
* the excess, and the field is gone from the next read. A move already
|
|
968
|
-
* booked says the same of itself ({@link ScheduledChange.excess}). Which
|
|
969
|
-
* kinds count is the platform's to decide; a client renders the keys it is
|
|
970
|
-
* given.
|
|
971
|
-
*/
|
|
972
|
-
readonly excess?: Partial<Caps>;
|
|
973
960
|
}
|
|
974
961
|
/**
|
|
975
962
|
* Acknowledgement of `DELETE /account` (202). Termination is asynchronous —
|
|
@@ -2499,9 +2486,10 @@ interface PlansResponse {
|
|
|
2499
2486
|
* Schedule that applies the change at period end. The answer says which
|
|
2500
2487
|
* happened ({@link PlanChangeResponse}).
|
|
2501
2488
|
*
|
|
2502
|
-
* A move down a tier is
|
|
2503
|
-
*
|
|
2504
|
-
*
|
|
2489
|
+
* A move down a tier is booked only by an account that fits it: while the
|
|
2490
|
+
* account holds more members or domains than the destination allows, the
|
|
2491
|
+
* door refuses (400) with a sentence naming what to remove, and the same
|
|
2492
|
+
* counts in `details.excess`, keyed like {@link Caps}.
|
|
2505
2493
|
*/
|
|
2506
2494
|
interface PlanChangeRequest {
|
|
2507
2495
|
readonly plan: AccountPlanType;
|
|
@@ -2523,20 +2511,6 @@ interface ScheduledChange {
|
|
|
2523
2511
|
readonly plan: AccountPlanType;
|
|
2524
2512
|
readonly interval: BillingInterval;
|
|
2525
2513
|
readonly at: number;
|
|
2526
|
-
/**
|
|
2527
|
-
* What the account must remove before `at` to fit the booked plan: per
|
|
2528
|
-
* kind, how many, in {@link PlanDestination.excess}'s shape. A move down a
|
|
2529
|
-
* tier is booked by an account that fits it, so this is absent on the day
|
|
2530
|
-
* of booking and on the change door's answer. The account keeps its
|
|
2531
|
-
* current plan until the change applies, though, and may add a member or
|
|
2532
|
-
* a domain the booked plan has no room for; `GET /account` then counts
|
|
2533
|
-
* them here, for as long as the change is booked, whatever else the
|
|
2534
|
-
* account may or may not order meanwhile. It is a count to REMOVE, not of
|
|
2535
|
-
* what pauses: holdings that do not fit when the change applies are
|
|
2536
|
-
* paused by the platform's own rule, which for members pauses every
|
|
2537
|
-
* member while the account is over. Absent while the account fits.
|
|
2538
|
-
*/
|
|
2539
|
-
readonly excess?: Partial<Caps>;
|
|
2540
2514
|
}
|
|
2541
2515
|
/**
|
|
2542
2516
|
* The answer of `POST /billing/change` — exactly one field is set, and the
|