sinfactura-types 1.6.2 → 1.6.4

package/dist/cash.d.ts

@@ -9,6 +9,11 @@ declare global {
         outcome?: number;
         balance?: number;
         subject?: string;
+        currency?: string;
+        currencyValue?: number;
+        currencyValueAt?: number;
+        balanceByCurrency?: Record<string, number>;
+        incomeByCurrency?: Record<string, number>;
     }
 }
 export {};

package/dist/payment.d.ts

@@ -1,107 +1,110 @@
-/**
- * WebSocket broadcast payload for the `payment_received` action.
- *
- * Fired by the API when a "money received" event is persisted across any
- * of three sources (MP webhook, Stripe webhook, MP movements poller).
- * Receivers (FE) should:
- *   1. Render an immediate snackbar toast using `total` + `currency` + `payerName`.
- *   2. Invalidate RTK Query tags `PaymentReceived` + `PaymentReceivedUnlinked`
- *      so the canonical row is refetched from `GET /payments/received`.
- */
-export type PaymentReceivedSource = "mp" | "stripe" | "mp_movement";
-export interface PaymentReceivedWsPayload {
-    source: PaymentReceivedSource;
-    paymentId: string;
-    total: number;
-    currency: string;
-    payerName?: string;
-    paidAt: number;
-    customerId?: string;
-    orderId?: string;
-    invoiceId?: string;
-}
-/**
- * REST shape of a payment row returned by `GET /payments/received` (api#902).
- *
- * Distinct from `PaymentReceivedWsPayload` (api#880, the WS broadcast):
- *   - This carries denormalized labels (customerName, orderCode, invoiceCode)
- *     attached server-side at response time so the FE doesn't N+1 fetch.
- *   - The WS broadcast is the lean live-tail event; this is the canonical row.
- */
-export interface PaymentReceived {
-    paymentId: string;
-    source: PaymentReceivedSource;
-    total: number;
-    currency: string;
-    currencyValue?: number;
-    currencyValueAt?: number;
-    payerName?: string;
-    payerEmail?: string;
-    payerCuit?: string;
-    paidAt: number;
-    customerId?: string;
-    customerName?: string;
-    orderId?: string;
-    orderCode?: string;
-    invoiceId?: string;
-    invoiceCode?: string;
-    accountId?: string;
-    linkedAt?: number;
-    linkSource?: "auto" | "manual";
-}
-/**
- * Confidence tier for a link suggestion (api#904).
- *
- * Mapped from heuristic match strength:
- *   - 'Alta': customer CUIT/email exact OR order amount-exact + ±24h
- *   - 'Media': order amount ±5% within ±7d
- *   - 'Baja': reserved for future broader heuristics (currently unused)
- */
-export type LinkSuggestionConfidence = "Alta" | "Media" | "Baja";
-/**
- * One ranked customer candidate for a payment's link dialog (api#904).
- * The FE renders the chip with `fullName`, the confidence badge, and the
- * `reason` text verbatim.
- */
-export interface CustomerCandidate {
-    customerId: string;
-    fullName: string;
-    cuit?: string;
-    email?: string;
-    confidence: LinkSuggestionConfidence;
-    reason: string;
-    score: number;
-}
-/**
- * One ranked order candidate for a payment's link dialog (api#904).
- * `orderCode` is currently identical to `orderId` (no separate short code
- * field on Order today); kept as a distinct field for forward-compat with
- * a future Order.code rollout.
- *
- * `currency` is always 'ARS' in v1 (the storage currency for SINFACTURA's
- * Argentine tenants); USD-priced orders surface their ARS-equivalent total.
- * `total` is therefore in ARS regardless of how the order was originally
- * priced; FE may derive USD display from `Order.currency` (the FX rate)
- * if needed.
- */
-export interface OrderCandidate {
-    orderId: string;
-    orderCode: string;
-    customerId: string;
-    customerName: string;
-    total: number;
-    currency: string;
-    dated: number;
-    confidence: LinkSuggestionConfidence;
-    reason: string;
-    score: number;
-}
-/**
- * Response shape of `GET /payments/{source}/{paymentId}/link-suggestions`.
- * Both arrays may be empty when no signal — FE renders "Sin sugerencias
- * automáticas" and falls back to manual customer / order search inputs.
- */
-export interface LinkSuggestionsResponse {
-    customers: CustomerCandidate[];
-    orders: OrderCandidate[];
+declare global {
+    /**
+     * WebSocket broadcast payload for the `payment_received` action.
+     *
+     * Fired by the API when a "money received" event is persisted across any
+     * of three sources (MP webhook, Stripe webhook, MP movements poller).
+     * Receivers (FE) should:
+     *   1. Render an immediate snackbar toast using `total` + `currency` + `payerName`.
+     *   2. Invalidate RTK Query tags `PaymentReceived` + `PaymentReceivedUnlinked`
+     *      so the canonical row is refetched from `GET /payments/received`.
+     */
+    type PaymentReceivedSource = "mp" | "stripe" | "mp_movement";
+    interface PaymentReceivedWsPayload {
+        source: PaymentReceivedSource;
+        paymentId: string;
+        total: number;
+        currency: string;
+        payerName?: string;
+        paidAt: number;
+        customerId?: string;
+        orderId?: string;
+        invoiceId?: string;
+    }
+    /**
+     * REST shape of a payment row returned by `GET /payments/received` (api#902).
+     *
+     * Distinct from `PaymentReceivedWsPayload` (api#880, the WS broadcast):
+     *   - This carries denormalized labels (customerName, orderCode, invoiceCode)
+     *     attached server-side at response time so the FE doesn't N+1 fetch.
+     *   - The WS broadcast is the lean live-tail event; this is the canonical row.
+     */
+    interface PaymentReceived {
+        paymentId: string;
+        source: PaymentReceivedSource;
+        total: number;
+        currency: string;
+        currencyValue?: number;
+        currencyValueAt?: number;
+        payerName?: string;
+        payerEmail?: string;
+        payerCuit?: string;
+        paidAt: number;
+        customerId?: string;
+        customerName?: string;
+        orderId?: string;
+        orderCode?: string;
+        invoiceId?: string;
+        invoiceCode?: string;
+        accountId?: string;
+        linkedAt?: number;
+        linkSource?: "auto" | "manual";
+    }
+    /**
+     * Confidence tier for a link suggestion (api#904).
+     *
+     * Mapped from heuristic match strength:
+     *   - 'Alta': customer CUIT/email exact OR order amount-exact + ±24h
+     *   - 'Media': order amount ±5% within ±7d
+     *   - 'Baja': reserved for future broader heuristics (currently unused)
+     */
+    export type LinkSuggestionConfidence = "Alta" | "Media" | "Baja";
+    /**
+     * One ranked customer candidate for a payment's link dialog (api#904).
+     * The FE renders the chip with `fullName`, the confidence badge, and the
+     * `reason` text verbatim.
+     */
+    interface CustomerCandidate {
+        customerId: string;
+        fullName: string;
+        cuit?: string;
+        email?: string;
+        confidence: LinkSuggestionConfidence;
+        reason: string;
+        score: number;
+    }
+    /**
+     * One ranked order candidate for a payment's link dialog (api#904).
+     * `orderCode` is currently identical to `orderId` (no separate short code
+     * field on Order today); kept as a distinct field for forward-compat with
+     * a future Order.code rollout.
+     *
+     * `currency` is always 'ARS' in v1 (the storage currency for SINFACTURA's
+     * Argentine tenants); USD-priced orders surface their ARS-equivalent total.
+     * `total` is therefore in ARS regardless of how the order was originally
+     * priced; FE may derive USD display from `Order.currency` (the FX rate)
+     * if needed.
+     */
+    interface OrderCandidate {
+        orderId: string;
+        orderCode: string;
+        customerId: string;
+        customerName: string;
+        total: number;
+        currency: string;
+        dated: number;
+        confidence: LinkSuggestionConfidence;
+        reason: string;
+        score: number;
+    }
+    /**
+     * Response shape of `GET /payments/{source}/{paymentId}/link-suggestions`.
+     * Both arrays may be empty when no signal — FE renders "Sin sugerencias
+     * automáticas" and falls back to manual customer / order search inputs.
+     */
+    interface LinkSuggestionsResponse {
+        customers: CustomerCandidate[];
+        orders: OrderCandidate[];
+    }
 }
+export {};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sinfactura-types",
-  "version": "1.6.2",
+  "version": "1.6.4",
   "main": "dist/index.js",
   "type": "module",
   "types": "./dist/index.d.ts",