@zeniai/client-epic-state 5.0.65-betaRR2 → 5.0.65-betaRR4

package/lib/entity/cardPolicy/cardPolicyPayload.d.ts

@@ -49,7 +49,7 @@ interface CardPolicyTemplateEntityListPayload {
     merchant_names: string[];
 }
 interface CardPolicyTemplateSpendLimitsPayload {
-    transaction: number;
+    transaction: number | null;
 }
 /**
  * Request body for `POST /cards/1.0/policy-templates`. Consumers pass the
@@ -63,7 +63,12 @@ export interface CreateCardPolicyTemplateRequest {
     description: string;
     mode: CardPolicyTemplateMode;
     name: string;
-    requiredReceiptThreshold: number;
+    /**
+     * `null` indicates the require-receipt toggle is off (no threshold
+     * configured). The BE accepts `null` and treats it as "no requirement";
+     * `0` means the user explicitly entered zero with the toggle on.
+     */
+    requiredReceiptThreshold: number | null;
     spendLimits: CardPolicyTemplateSpendLimits;
 }
 export interface CreateCardPolicyTemplateRequestBody {
@@ -73,7 +78,7 @@ export interface CreateCardPolicyTemplateRequestBody {
     description: string;
     mode: string;
     name: string;
-    required_receipt_threshold: number;
+    required_receipt_threshold: number | null;
     spend_limits: CardPolicyTemplateSpendLimitsPayload;
 }
 export interface CardPolicyTemplatePayload {
@@ -87,7 +92,7 @@ export interface CardPolicyTemplatePayload {
     description: string;
     mode: string;
     name: string;
-    required_receipt_threshold: number;
+    required_receipt_threshold: number | null;
     spend_limits: CardPolicyTemplateSpendLimitsPayload;
     status: string;
     template_id: ID;

package/lib/entity/cardPolicy/cardPolicyState.d.ts

@@ -30,9 +30,14 @@ export interface CardPolicyTemplateEntityList {
  * Spend-limit caps configured per template. Only `transaction` is modeled
  * today; additional cadences (e.g. daily, monthly) will be added if/when
  * the backend exposes them.
+ *
+ * `transaction` is `number | null`: `null` means the row's toggle is off
+ * (no limit configured), `0` means the user explicitly entered zero with
+ * the toggle on, and any positive value is the configured per-transaction
+ * cap.
  */
 export interface CardPolicyTemplateSpendLimits {
-    transaction: number;
+    transaction: number | null;
 }
 /**
  * Mapped (camelCase) representation of a card-policy template returned by
@@ -51,7 +56,12 @@ export interface CardPolicyTemplate {
     description: string;
     mode: CardPolicyTemplateMode;
     name: string;
-    requiredReceiptThreshold: number;
+    /**
+     * Receipt-required threshold in dollars. `null` means the toggle is off
+     * (no receipt requirement); `0` means the user explicitly entered zero
+     * with the toggle on; any positive value is the configured threshold.
+     */
+    requiredReceiptThreshold: number | null;
     spendLimits: CardPolicyTemplateSpendLimits;
     status: CardPolicyTemplateStatus;
     templateId: ID;

package/lib/esm/view/aiCfoView/epics/fetchSuggestedQuestionsEpic.js

@@ -2,13 +2,23 @@ import { of } from 'rxjs';
 import { catchError, filter, mergeMap } from 'rxjs/operators';
 import { createZeniAPIStatus, isSuccessResponse } from '../../../responsePayload';
 import { fetchSuggestedQuestions, fetchSuggestedQuestionsFailure, fetchSuggestedQuestionsSuccess, } from '../aiCfoViewReducer';
-/** GET {aiCfoMicroServiceBaseUrl}/1.0/suggested-questions?page_context=... */
+/**
+ * GET {aiCfoMicroServiceBaseUrl}/1.0/suggested-questions?page_context=...
+ *
+ * Appends `&no_card_created=true` when the action payload sets
+ * `noCardCreated: true` (AI Card Creation flow on the cards list — the tenant
+ * has not yet created any card). Any other value omits the flag entirely so
+ * the existing call sites continue to issue the unchanged request.
+ */
 export const fetchSuggestedQuestionsEpic = (actions$, _state$, zeniAPI) => actions$.pipe(filter(fetchSuggestedQuestions.match), 
 // mergeMap (not switchMap): each page_context is keyed separately in Redux; switchMap
 // would cancel in-flight HTTP for context A when B is requested, leaving A stuck In-Progress.
 mergeMap((action) => {
-    const { pageContext } = action.payload;
+    const { pageContext, noCardCreated } = action.payload;
     const query = new URLSearchParams({ page_context: pageContext });
+    if (noCardCreated === true) {
+        query.set('no_card_created', 'true');
+    }
     const url = `${zeniAPI.apiEndPoints.aiCfoMicroServiceBaseUrl}/1.0/suggested-questions?${query.toString()}`;
     return zeniAPI.getJSON(url).pipe(mergeMap((response) => {
         if (isSuccessResponse(response) && response.data != null) {

package/lib/esm/view/spendManagement/chargeCards/cardPolicy/cardPolicyDetail/fetchCardPolicyDetailEpic.js

@@ -1,8 +1,8 @@
 import { from, of } from 'rxjs';
-import { catchError, filter, mergeMap } from 'rxjs/operators';
+import { catchError, exhaustMap, filter, mergeMap } from 'rxjs/operators';
 import { toCardPolicyEditFormDraft, toCardPolicyTemplate, } from '../../../../../entity/cardPolicy/cardPolicyPayload';
 import { updateCreatedCardPolicyTemplate } from '../../../../../entity/cardPolicy/cardPolicyReducer';
-import { createZeniAPIStatus, isSuccessStatus } from '../../../../../responsePayload';
+import { createZeniAPIStatus, isSuccessStatus, } from '../../../../../responsePayload';
 import { fetchCardPolicyDetail, updateCardPolicyDetailFetchStatus, updateCardPolicyFormDraft, } from './cardPolicyDetailReducer';
 /**
  * `GET /cards/1.0/policy-templates/{id}`. Response is the same
@@ -15,7 +15,19 @@ import { fetchCardPolicyDetail, updateCardPolicyDetailFetchStatus, updateCardPol
  *      the page can render with the existing values pre-populated.
  *   3. Flip the view lifecycle to `Completed` / `Error`.
  */
-export const fetchCardPolicyDetailEpic = (actions$, _state$, zeniAPI) => actions$.pipe(filter(fetchCardPolicyDetail.match), mergeMap((action) => {
+export const fetchCardPolicyDetailEpic = (actions$, _state$, zeniAPI) => actions$.pipe(filter(fetchCardPolicyDetail.match), 
+// `exhaustMap` (rather than `mergeMap`) so a duplicate
+// `fetchCardPolicyDetail` dispatched while the previous one is
+// still in flight is dropped instead of producing a second HTTP
+// request. The edit screen dispatches this on mount, and React 18
+// StrictMode invokes its mount effect twice with a stale
+// `detailFetchState` closure — without `exhaustMap` that yields
+// two `/policy-templates/{id}` calls. (The screen also dedupes
+// list→edit navigations via the entity-cached template, so the
+// detail GET is only emitted on direct landings — there's no
+// realistic cross-templateId scenario that needs cancel-and-retry
+// semantics here.)
+exhaustMap((action) => {
     const templateId = action.payload;
     return zeniAPI
         .getJSON(`${zeniAPI.apiEndPoints.cardMicroServiceBaseUrl}/1.0/policy-templates/${templateId}`)

package/lib/esm/view/spendManagement/chargeCards/cardPolicy/cardPolicyList/fetchCardPolicyListEpic.js

@@ -1,8 +1,8 @@
 import { from, of } from 'rxjs';
-import { catchError, filter, mergeMap } from 'rxjs/operators';
+import { catchError, exhaustMap, filter, mergeMap } from 'rxjs/operators';
 import { toCardPolicyStats, toCardPolicyTemplateList, } from '../../../../../entity/cardPolicy/cardPolicyPayload';
 import { updateCardPolicyStats, updateCardPolicyTemplates, } from '../../../../../entity/cardPolicy/cardPolicyReducer';
-import { createZeniAPIStatus, isSuccessStatus } from '../../../../../responsePayload';
+import { createZeniAPIStatus, isSuccessStatus, } from '../../../../../responsePayload';
 import { fetchCardPolicyList, updateCardPolicyListFetchStatus, } from './cardPolicyListReducer';
 /**
  * `GET /cards/1.0/policy-templates`. On success the response carries
@@ -15,7 +15,17 @@ import { fetchCardPolicyList, updateCardPolicyListFetchStatus, } from './cardPol
  *   2. `updateCardPolicyStats` — entity-level cached stats.
  *   3. `updateCardPolicyListFetchStatus` — view lifecycle + ordered IDs.
  */
-export const fetchCardPolicyListEpic = (actions$, _state$, zeniAPI) => actions$.pipe(filter(fetchCardPolicyList.match), mergeMap(() => {
+export const fetchCardPolicyListEpic = (actions$, _state$, zeniAPI) => actions$.pipe(filter(fetchCardPolicyList.match), 
+// `exhaustMap` (rather than `mergeMap`) so a duplicate
+// `fetchCardPolicyList` dispatched while the previous one is still
+// in flight is dropped instead of producing a second HTTP request.
+// This guards against React 18 StrictMode, which mount-cleanup-
+// remounts the screen's mount effect with a stale closure of
+// `listFetchState`, causing the same effect to dispatch this
+// action twice synchronously. Retry-after-error still works
+// because the previous inner observable has completed by the time
+// the user retries.
+exhaustMap(() => {
     return zeniAPI
         .getJSON(`${zeniAPI.apiEndPoints.cardMicroServiceBaseUrl}/1.0/policy-templates`)
         .pipe(mergeMap((response) => {

package/lib/esm/view/spendManagement/chargeCards/cardPolicy/createCardPolicy/fetchCardPolicyMccCategoriesEpic.js

@@ -1,8 +1,16 @@
 import { from, of } from 'rxjs';
-import { catchError, filter, mergeMap } from 'rxjs/operators';
+import { catchError, exhaustMap, filter, mergeMap } from 'rxjs/operators';
 import { fetchCardPolicyMccCategories, updateCardPolicyMccCategories, updateCardPolicyMccCategoriesFailure, } from '../../../../../entity/cardPolicy/cardPolicyReducer';
-import { createZeniAPIStatus, isSuccessStatus } from '../../../../../responsePayload';
-export const fetchCardPolicyMccCategoriesEpic = (actions$, _state$, zeniAPI) => actions$.pipe(filter(fetchCardPolicyMccCategories.match), mergeMap(() => {
+import { createZeniAPIStatus, isSuccessStatus, } from '../../../../../responsePayload';
+export const fetchCardPolicyMccCategoriesEpic = (actions$, _state$, zeniAPI) => actions$.pipe(filter(fetchCardPolicyMccCategories.match), 
+// `exhaustMap` (rather than `mergeMap`) so a duplicate
+// `fetchCardPolicyMccCategories` dispatched while the previous one
+// is still in flight is dropped instead of producing a second HTTP
+// request. Both the Create and Edit policy screens dispatch this
+// on mount, and React 18 StrictMode invokes their mount effect
+// twice with a stale `mccCategoriesFetchState` closure — without
+// `exhaustMap` that yields two `/cards/mcc-codes` calls.
+exhaustMap(() => {
     return zeniAPI
         .getJSON(`${zeniAPI.apiEndPoints.cardMicroServiceBaseUrl}/1.0/cards/mcc-codes`)
         .pipe(mergeMap((response) => {

package/lib/view/aiCfoView/aiCfoViewReducer.d.ts

@@ -92,6 +92,13 @@ export declare const submitQuestion: import("@reduxjs/toolkit").ActionCreatorWit
     questionAnswerId: ID;
 }, "aiCfoView/updateCotCollapsedState">, fetchSuggestedQuestions: import("@reduxjs/toolkit").ActionCreatorWithPayload<{
     pageContext: AiCfoSuggestedQuestionsPageContext;
+    /**
+     * AI Card Creation flow: when true, the epic appends `&no_card_created=true`
+     * so the backend tailors prompts for a tenant that has not yet created a
+     * card. The bucket key is unchanged (`pageContext`); see
+     * `useFetchSuggestedQuestionsWhenReady` for the refetch-on-flag-flip rule.
+     */
+    noCardCreated?: boolean;
 }, "aiCfoView/fetchSuggestedQuestions">, fetchSuggestedQuestionsSuccess: import("@reduxjs/toolkit").ActionCreatorWithPayload<{
     generatedAt: string;
     pageContext: AiCfoSuggestedQuestionsPageContext;

package/lib/view/aiCfoView/epics/fetchSuggestedQuestionsEpic.d.ts

@@ -4,5 +4,12 @@ import { RootState } from '../../../reducer';
 import { ZeniAPI } from '../../../zeniAPI';
 import { fetchSuggestedQuestions, fetchSuggestedQuestionsFailure, fetchSuggestedQuestionsSuccess } from '../aiCfoViewReducer';
 export type ActionType = ReturnType<typeof fetchSuggestedQuestions> | ReturnType<typeof fetchSuggestedQuestionsSuccess> | ReturnType<typeof fetchSuggestedQuestionsFailure>;
-/** GET {aiCfoMicroServiceBaseUrl}/1.0/suggested-questions?page_context=... */
+/**
+ * GET {aiCfoMicroServiceBaseUrl}/1.0/suggested-questions?page_context=...
+ *
+ * Appends `&no_card_created=true` when the action payload sets
+ * `noCardCreated: true` (AI Card Creation flow on the cards list — the tenant
+ * has not yet created any card). Any other value omits the flag entirely so
+ * the existing call sites continue to issue the unchanged request.
+ */
 export declare const fetchSuggestedQuestionsEpic: (actions$: ActionsObservable<ActionType>, _state$: StateObservable<RootState>, zeniAPI: ZeniAPI) => Observable<ActionType>;

package/lib/view/aiCfoView/epics/fetchSuggestedQuestionsEpic.js

@@ -5,13 +5,23 @@ const rxjs_1 = require("rxjs");
 const operators_1 = require("rxjs/operators");
 const responsePayload_1 = require("../../../responsePayload");
 const aiCfoViewReducer_1 = require("../aiCfoViewReducer");
-/** GET {aiCfoMicroServiceBaseUrl}/1.0/suggested-questions?page_context=... */
+/**
+ * GET {aiCfoMicroServiceBaseUrl}/1.0/suggested-questions?page_context=...
+ *
+ * Appends `&no_card_created=true` when the action payload sets
+ * `noCardCreated: true` (AI Card Creation flow on the cards list — the tenant
+ * has not yet created any card). Any other value omits the flag entirely so
+ * the existing call sites continue to issue the unchanged request.
+ */
 const fetchSuggestedQuestionsEpic = (actions$, _state$, zeniAPI) => actions$.pipe((0, operators_1.filter)(aiCfoViewReducer_1.fetchSuggestedQuestions.match), 
 // mergeMap (not switchMap): each page_context is keyed separately in Redux; switchMap
 // would cancel in-flight HTTP for context A when B is requested, leaving A stuck In-Progress.
 (0, operators_1.mergeMap)((action) => {
-    const { pageContext } = action.payload;
+    const { pageContext, noCardCreated } = action.payload;
     const query = new URLSearchParams({ page_context: pageContext });
+    if (noCardCreated === true) {
+        query.set('no_card_created', 'true');
+    }
     const url = `${zeniAPI.apiEndPoints.aiCfoMicroServiceBaseUrl}/1.0/suggested-questions?${query.toString()}`;
     return zeniAPI.getJSON(url).pipe((0, operators_1.mergeMap)((response) => {
         if ((0, responsePayload_1.isSuccessResponse)(response) && response.data != null) {

package/lib/view/spendManagement/chargeCards/cardPolicy/cardPolicyDetail/fetchCardPolicyDetailEpic.js

@@ -18,7 +18,19 @@ const cardPolicyDetailReducer_1 = require("./cardPolicyDetailReducer");
  *      the page can render with the existing values pre-populated.
  *   3. Flip the view lifecycle to `Completed` / `Error`.
  */
-const fetchCardPolicyDetailEpic = (actions$, _state$, zeniAPI) => actions$.pipe((0, operators_1.filter)(cardPolicyDetailReducer_1.fetchCardPolicyDetail.match), (0, operators_1.mergeMap)((action) => {
+const fetchCardPolicyDetailEpic = (actions$, _state$, zeniAPI) => actions$.pipe((0, operators_1.filter)(cardPolicyDetailReducer_1.fetchCardPolicyDetail.match), 
+// `exhaustMap` (rather than `mergeMap`) so a duplicate
+// `fetchCardPolicyDetail` dispatched while the previous one is
+// still in flight is dropped instead of producing a second HTTP
+// request. The edit screen dispatches this on mount, and React 18
+// StrictMode invokes its mount effect twice with a stale
+// `detailFetchState` closure — without `exhaustMap` that yields
+// two `/policy-templates/{id}` calls. (The screen also dedupes
+// list→edit navigations via the entity-cached template, so the
+// detail GET is only emitted on direct landings — there's no
+// realistic cross-templateId scenario that needs cancel-and-retry
+// semantics here.)
+(0, operators_1.exhaustMap)((action) => {
     const templateId = action.payload;
     return zeniAPI
         .getJSON(`${zeniAPI.apiEndPoints.cardMicroServiceBaseUrl}/1.0/policy-templates/${templateId}`)

package/lib/view/spendManagement/chargeCards/cardPolicy/cardPolicyList/fetchCardPolicyListEpic.js

@@ -18,7 +18,17 @@ const cardPolicyListReducer_1 = require("./cardPolicyListReducer");
  *   2. `updateCardPolicyStats` — entity-level cached stats.
  *   3. `updateCardPolicyListFetchStatus` — view lifecycle + ordered IDs.
  */
-const fetchCardPolicyListEpic = (actions$, _state$, zeniAPI) => actions$.pipe((0, operators_1.filter)(cardPolicyListReducer_1.fetchCardPolicyList.match), (0, operators_1.mergeMap)(() => {
+const fetchCardPolicyListEpic = (actions$, _state$, zeniAPI) => actions$.pipe((0, operators_1.filter)(cardPolicyListReducer_1.fetchCardPolicyList.match), 
+// `exhaustMap` (rather than `mergeMap`) so a duplicate
+// `fetchCardPolicyList` dispatched while the previous one is still
+// in flight is dropped instead of producing a second HTTP request.
+// This guards against React 18 StrictMode, which mount-cleanup-
+// remounts the screen's mount effect with a stale closure of
+// `listFetchState`, causing the same effect to dispatch this
+// action twice synchronously. Retry-after-error still works
+// because the previous inner observable has completed by the time
+// the user retries.
+(0, operators_1.exhaustMap)(() => {
     return zeniAPI
         .getJSON(`${zeniAPI.apiEndPoints.cardMicroServiceBaseUrl}/1.0/policy-templates`)
         .pipe((0, operators_1.mergeMap)((response) => {

package/lib/view/spendManagement/chargeCards/cardPolicy/createCardPolicy/fetchCardPolicyMccCategoriesEpic.js

@@ -5,7 +5,15 @@ const rxjs_1 = require("rxjs");
 const operators_1 = require("rxjs/operators");
 const cardPolicyReducer_1 = require("../../../../../entity/cardPolicy/cardPolicyReducer");
 const responsePayload_1 = require("../../../../../responsePayload");
-const fetchCardPolicyMccCategoriesEpic = (actions$, _state$, zeniAPI) => actions$.pipe((0, operators_1.filter)(cardPolicyReducer_1.fetchCardPolicyMccCategories.match), (0, operators_1.mergeMap)(() => {
+const fetchCardPolicyMccCategoriesEpic = (actions$, _state$, zeniAPI) => actions$.pipe((0, operators_1.filter)(cardPolicyReducer_1.fetchCardPolicyMccCategories.match), 
+// `exhaustMap` (rather than `mergeMap`) so a duplicate
+// `fetchCardPolicyMccCategories` dispatched while the previous one
+// is still in flight is dropped instead of producing a second HTTP
+// request. Both the Create and Edit policy screens dispatch this
+// on mount, and React 18 StrictMode invokes their mount effect
+// twice with a stale `mccCategoriesFetchState` closure — without
+// `exhaustMap` that yields two `/cards/mcc-codes` calls.
+(0, operators_1.exhaustMap)(() => {
     return zeniAPI
         .getJSON(`${zeniAPI.apiEndPoints.cardMicroServiceBaseUrl}/1.0/cards/mcc-codes`)
         .pipe((0, operators_1.mergeMap)((response) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zeniai/client-epic-state",
-  "version": "5.0.65-betaRR2",
+  "version": "5.0.65-betaRR4",
   "description": "Shared module between Web & Mobile containing required abstractions for state management, async network communication. ",
   "main": "lib/index.js",
   "module": "lib/esm/index.js",