@getmicdrop/venue-calendar 4.3.56 → 4.3.58

package/dist/api/cart-addons.d.ts

@@ -0,0 +1,61 @@
+/**
+ * ADD-ONS ON A CART THAT IS ALREADY BEING PAID FOR (MIC-4326).
+ *
+ * Why this is not `updateCartQuantities`. The cart PUT carries only
+ * `quantities` / `donationAmounts` — there is no add-on field on it — and
+ * orders-service guards that route with `rejectIfPriced`, which refuses every
+ * mutation of a cart holding a PaymentIntent. `initializeStripePayment()` runs on
+ * checkout MOUNT, so on the checkout page the cart always has one. A PUT from
+ * here would 409 every time.
+ *
+ * `POST /cart/:uuid/add-ons` is the gift-card door instead: it reprices rather
+ * than refusing — cancelling the stale PaymentIntent so a secret priced without
+ * the t-shirt can never be confirmed — and tells us whether it did.
+ *
+ * NO BUYER-FACING COPY IN THIS FILE, deliberately: VC's l10n gates do not scan
+ * `api/*.ts`, so a hardcoded English sentence here would ship untranslated and
+ * unnoticed. Refusals are surfaced one of two ways — the SERVER's own message
+ * (which is already buyer-readable and localisation-free in the sense that it
+ * names the operator's own product: "Tour t-shirt just sold out"), or, when there
+ * is none, a `null` that the calling component renders from its own labels.
+ */
+/** One add-on line as the cart now holds it. Money is CENTS, as everywhere add-ons are. */
+export interface CartAddOnLine {
+    addOnId: number;
+    name: string;
+    quantity: number;
+    priceCents: number;
+    lineTotalCents: number;
+}
+export interface CartAddOnsResult {
+    success: boolean;
+    /**
+     * The server's refusal sentence, when it gave one. `null` means "no usable
+     * message" and the caller must fall back to its own labelled copy.
+     */
+    error: string | null;
+    lines: CartAddOnLine[];
+    addOnQuantity: number;
+    /**
+     * THE FIELD THE CALLER CANNOT SKIP. True means the cart's PaymentIntent was
+     * thrown away and a fresh one must be minted before the buyer can pay.
+     * Inferring this from "no error" would either strand the buyer against a dead
+     * secret or re-mint a perfectly good intent for nothing.
+     *
+     * False on an unchanged cart (an identical re-send short-circuits server-side)
+     * and false on failure, because nothing was repriced.
+     */
+    repriced: boolean;
+}
+/**
+ * Set the add-ons on an existing cart.
+ *
+ * ABSOLUTE, NOT A DELTA — the map is the desired end state ("2 tees"), matching
+ * `addOnQuantities` on cart-create. A delta cannot be retried safely: a dropped
+ * response leaves us unable to tell whether an increment landed, and re-sending
+ * buys a second shirt. The buyer's retry here is a finger on a `+` button, so
+ * idempotence is not theoretical.
+ *
+ * An EMPTY map removes every add-on; there is no separate delete call.
+ */
+export declare function updateCartAddOns(cartId: string, quantities: Record<string | number, number>): Promise<CartAddOnsResult>;

package/dist/api/index.d.ts

@@ -30,14 +30,16 @@
  * ```
  */
 export { configureApi, getApiConfig, getPublicBaseUrl, getLegacyPublicUrl, getOrdersV2Url, getClientIP, apiGet, apiPost, apiPut, apiDelete, } from './client.js';
-export { createPaymentIntent, validatePaymentIntent, updateCartQuantities, getCartByUUID, createOrder, getOrder, completeReservation, cancelReservation, extendCheckoutSession, getSessionStatus, initiateOrder, trackUTMSource, } from './orders.js';
-export type { CartReservationView, CartView } from './orders.js';
+export { createPaymentIntent, submitCheckoutAnswers, validatePaymentIntent, updateCartQuantities, getCartByUUID, createOrder, getOrder, completeReservation, cancelReservation, extendCheckoutSession, getSessionStatus, initiateOrder, trackUTMSource, } from './orders.js';
+export type { CartReservationView, CartView, CheckoutAnswersResult, } from './orders.js';
 export { validatePromoCode, hasPromoCodes, applyPromoCode, removePromoCode, } from './promo.js';
 export { fetchEventDetails, fetchEventTickets, fetchEventPerformers, fetchAllVenues, fetchVenueEvents, getMonthEvents, getOrgMonthEvents, getSeriesOccurrences, fetchSeriesOccurrences, fetchPublicCollection, resolvePublicEntity, checkEventPassword, checkCollectionPassword, testNetworkConnection, fetchEventDetailsResult, fetchEventTicketsResult, fetchEventPerformersResult, fetchAllVenuesResult, fetchVenueEventsResult, getMonthEventsResult, getOrgMonthEventsResult, getSeriesOccurrencesResult, fetchSeriesOccurrencesResult, } from './events.js';
 export { ok, err, errNotFound, isOk, isErr, unwrapOr, type Result, } from './result.js';
 export { getVenue, getVenueFees, getVenueBySlug, hasPublishedSite, } from './venues.js';
 export { createGiftCardPurchase, applyGiftCard, removeGiftCard, completeGiftCardPayment, } from './gift-cards.js';
 export type { GiftCardPurchaseRequest, GiftCardPurchaseResponse, ApplyGiftCardResult, RemoveGiftCardResult, CompleteGiftCardPaymentInput, CompleteGiftCardPaymentResult, } from './gift-cards.js';
+export { updateCartAddOns } from './cart-addons.js';
+export type { CartAddOnLine, CartAddOnsResult } from './cart-addons.js';
 export { joinWaitlist, getWaitlistStatus, validateWaitlistToken, requeueWaitlistToFront, formatWaitlistWindow, } from './waitlist.js';
 export type { JoinWaitlistResult, WaitlistStatusResult, ValidateWaitlistTokenResult, RequeueWaitlistResult, } from './waitlist.js';
 export { computeCtaState } from './cta.js';

package/dist/api/orders.d.ts

@@ -26,6 +26,54 @@ export interface FreeOrderBuyer {
     mailingList?: boolean;
 }
 export declare function createPaymentIntent(cartId: string, quantities: Record<string | number, number>, donationAmounts?: Record<string | number, number>, buyer?: FreeOrderBuyer, uiLocale?: string): Promise<PaymentIntentResponse | null>;
+/** What the server said about a submission's checkout answers. */
+export interface CheckoutAnswersResult {
+    /**
+     * The venue's refusal, worded by the SERVER, or null when there was none.
+     *
+     * It NAMES the missing field, which is why it is carried as the message
+     * itself rather than as a boolean the caller then has to write copy for: a
+     * house string would put the buyer in front of a checkout that refuses
+     * without saying what is wrong. Truthiness is the whole contract -- a caller
+     * that finds a string here must not charge.
+     */
+    refusal: string | null;
+    /**
+     * The PaymentIntent this cart is payable against, when nothing was refused.
+     * The caller compares it with the secret its Stripe element is mounted on.
+     */
+    clientSecret?: string;
+}
+/**
+ * Put the buyer's checkout answers in front of the server on the CARD path,
+ * before anything is charged.
+ *
+ * WHY THIS CALL EXISTS. The venue's `requiredPhoneAtCheckout` /
+ * `requiredCustomCheckout` flags are enforced in orders-service, and that guard
+ * fires on any payment-intent request that identifies the buyer. The card path
+ * never made such a request: the PaymentIntent is minted on checkout MOUNT,
+ * deliberately anonymous so no order is created before the buyer has typed
+ * anything, and nothing after it is refusable -- ValidatePaymentIntent runs
+ * against a PaymentIntent Stripe has already reported `succeeded`, so a refusal
+ * there would take the money and withhold the ticket. PaymentIntent creation is
+ * the last door, so the answers are sent to it, and the server's existing guard
+ * then covers the card path with no change on its side.
+ *
+ * SENT UNCONDITIONALLY, not gated on the widget's own reading of the flags. The
+ * point is that the SERVER decides; a client that only calls when it already
+ * believes a field is required is back to the form being the only gate.
+ *
+ * SAFE TO REPEAT. The Stripe idempotency key orders-service derives covers every
+ * charge-determining field (amount, fees, destination, promo, gift card, reprice
+ * generation) and no buyer field, so an unchanged cart resolves to the SAME
+ * PaymentIntent and the mounted Stripe element stays valid. `clientSecret` is
+ * handed back anyway so the caller can assert that rather than assume it.
+ *
+ * FAILS OPEN on anything that is not the explicit refusal -- a network blip must
+ * not block a checkout that would otherwise have gone through, the same way the
+ * server's own guard lets an unreadable venue pass.
+ */
+export declare function submitCheckoutAnswers(cartId: string, quantities: Record<string | number, number>, donationAmounts: Record<string | number, number> | undefined, buyer: FreeOrderBuyer, uiLocale?: string): Promise<CheckoutAnswersResult>;
 /**
  * Fetch an existing cart by UUID (cross-device pre-fill — §1.3).
  *

package/dist/api/transformers/venue.d.ts

@@ -40,7 +40,7 @@ declare function vcFormatVenueAddress(venue: Venue): string;
 /**
  * The venue's checkout settings, as the checkout form needs them.
  *
- * These four keys describe what the checkout asks a buyer for, so the ONLY
+ * These five keys describe what the checkout asks a buyer for, so the ONLY
  * consumer is CheckoutForm — every EventData shaper pulls them off whatever
  * venue block its payload carries and hands them down. Kept here, beside
  * extractVenueFees, because they are venue config read out of a raw venue
@@ -53,6 +53,18 @@ declare function vcFormatVenueAddress(venue: Venue): string;
  * anyway — the widget is pinned by version and runs against whatever API the
  * host site's embed reaches, so it must not depend on the payload being current.
  *
+ * BOTH require-flags are DEPENDENT fields and both are re-derived here, never
+ * passed through raw. The raw columns can contradict each other (a row written
+ * before the operator form grew its own guard, a CSV import, an operator who
+ * ticked "require" and then blanked the question), and the rule the server
+ * enforces in orders-service `CheckoutSettings()` is the one that matters:
+ * NEVER DEMAND AN ANSWER TO A FIELD THE STOREFRONT DOES NOT RENDER. So
+ * `requiredPhoneAtCheckout` dies with `ask`, and `requiredCustomCheckout` dies
+ * with the normalized `hasCustomCheckout` — which is itself already false
+ * unless there is a non-blank prompt to show. Read the raw flag instead and a
+ * stale require=true/prompt='' row gives the buyer an unsatisfiable form: an
+ * error about a question that is not on the page.
+ *
  * A MISSING key defaults to "ask for a phone, don't require it, ask nothing
  * else": the least surprising checkout, and the one a payload that predates
  * these keys should still produce.
@@ -61,6 +73,7 @@ declare function vcExtractVenueCheckoutSettings(raw: unknown): {
     askForPhoneAtCheckout: boolean;
     requiredPhoneAtCheckout: boolean;
     hasCustomCheckout: boolean;
+    requiredCustomCheckout: boolean;
     questionPrompt: string | undefined;
 };
 export { vcExtractVenueFees as extractVenueFees, vcExtractVenueCheckoutSettings as extractVenueCheckoutSettings, vcFormatVenueAddress as formatVenueAddress, };