@shipstatic/ship 3.4.0-beta.4 → 3.4.0-beta.5

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/index.d.cts CHANGED
@@ -962,10 +962,12 @@ interface PlanDestination {
962
962
  /**
963
963
  * What the account holds beyond what this plan allows: per kind, how many
964
964
  * to remove. Present only on a cheaper tier the account does not fit, and
965
- * then never empty. A move down a tier pauses nothing, so the change door
966
- * refuses it until the account fits: the owner removes the excess, and the
967
- * field is gone from the next read. Which kinds count is the platform's to
968
- * decide; a client renders the keys it is given.
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.
969
971
  */
970
972
  readonly excess?: Partial<Caps>;
971
973
  }
@@ -2499,8 +2501,7 @@ interface PlansResponse {
2499
2501
  *
2500
2502
  * A move down a tier is refused while the account holds more than the
2501
2503
  * destination allows (400, `details.excess` in {@link PlanDestination.excess}'s
2502
- * shape): nothing is paused for a change the owner chose, so the account fits
2503
- * first.
2504
+ * shape): it is booked only by an account that fits it.
2504
2505
  */
2505
2506
  interface PlanChangeRequest {
2506
2507
  readonly plan: AccountPlanType;
@@ -2522,6 +2523,20 @@ interface ScheduledChange {
2522
2523
  readonly plan: AccountPlanType;
2523
2524
  readonly interval: BillingInterval;
2524
2525
  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>;
2525
2540
  }
2526
2541
  /**
2527
2542
  * The answer of `POST /billing/change` — exactly one field is set, and the
package/dist/index.d.ts CHANGED
@@ -962,10 +962,12 @@ interface PlanDestination {
962
962
  /**
963
963
  * What the account holds beyond what this plan allows: per kind, how many
964
964
  * to remove. Present only on a cheaper tier the account does not fit, and
965
- * then never empty. A move down a tier pauses nothing, so the change door
966
- * refuses it until the account fits: the owner removes the excess, and the
967
- * field is gone from the next read. Which kinds count is the platform's to
968
- * decide; a client renders the keys it is given.
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.
969
971
  */
970
972
  readonly excess?: Partial<Caps>;
971
973
  }
@@ -2499,8 +2501,7 @@ interface PlansResponse {
2499
2501
  *
2500
2502
  * A move down a tier is refused while the account holds more than the
2501
2503
  * destination allows (400, `details.excess` in {@link PlanDestination.excess}'s
2502
- * shape): nothing is paused for a change the owner chose, so the account fits
2503
- * first.
2504
+ * shape): it is booked only by an account that fits it.
2504
2505
  */
2505
2506
  interface PlanChangeRequest {
2506
2507
  readonly plan: AccountPlanType;
@@ -2522,6 +2523,20 @@ interface ScheduledChange {
2522
2523
  readonly plan: AccountPlanType;
2523
2524
  readonly interval: BillingInterval;
2524
2525
  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>;
2525
2540
  }
2526
2541
  /**
2527
2542
  * The answer of `POST /billing/change` — exactly one field is set, and the