@zeniai/client-epic-state 5.1.60 → 5.1.61-betaDI0

package/lib/esm/view/notificationPreferencesView/notificationPreferencesViewReducer.js

@@ -0,0 +1,222 @@
+import { createSlice } from '@reduxjs/toolkit';
+import { mapPayloadToPreferences, } from './notificationPreferencesViewPayload';
+import { emptyNotificationPreferences, } from './notificationPreferencesViewState';
+export const initialState = {
+    cancelEpoch: 0,
+    localOverrides: emptyNotificationPreferences(),
+    preferences: emptyNotificationPreferences(),
+    saveEpoch: 0,
+    savePreferencesState: { fetchState: 'Not-Started' },
+};
+const mergePreferences = (base, patch) => {
+    const eventEnabledByChannel = {
+        ...base.eventEnabledByChannel,
+    };
+    Object.entries(patch.eventEnabledByChannel).forEach(([eventId, channels]) => {
+        eventEnabledByChannel[eventId] = {
+            ...(base.eventEnabledByChannel[eventId] ?? {}),
+            ...channels,
+        };
+    });
+    return {
+        eventEnabledByChannel,
+        groupFrequencyByGroupId: {
+            ...base.groupFrequencyByGroupId,
+            ...patch.groupFrequencyByGroupId,
+        },
+    };
+};
+// Remove only the (eventId, channel) and groupId keys that were actually saved
+// to the server from `localOverrides` — AND whose current value still equals
+// what was saved. Any new edits the user added while the PUT was in flight
+// (either new keys not present in `saved`, OR same keys the user flipped back
+// to a different value) are preserved so the next debounce cycle picks them up.
+//
+// Presence-only subtraction (the prior implementation) silently dropped a
+// same-key re-edit that landed AFTER debounce fired but BEFORE the response
+// returned. Concrete case:
+//   1. toggle evt1.email = false → localOverrides = {evt1:{email:false}}
+//   2. debounce PUT #1 fires with savedOverrides = {evt1:{email:false}}
+//   3. user re-toggles evt1.email = true → localOverrides = {evt1:{email:true}}
+//   4. PUT #1 success → subtract dropped `email` on presence, so the true
+//      re-edit disappeared and next-debounce found nothing to send.
+const subtractSavedOverrides = (current, saved) => {
+    const eventEnabledByChannel = {};
+    Object.entries(current.eventEnabledByChannel).forEach(([eventId, channels]) => {
+        const savedChannels = saved.eventEnabledByChannel[eventId];
+        if (savedChannels == null) {
+            eventEnabledByChannel[eventId] = channels;
+            return;
+        }
+        const remainingChannels = {};
+        Object.keys(channels).forEach((channel) => {
+            // Preserve the key when it's a new channel OR when the user's
+            // current value differs from what was saved (same-key re-edit).
+            if (!(channel in savedChannels) ||
+                channels[channel] !== savedChannels[channel]) {
+                remainingChannels[channel] = channels[channel];
+            }
+        });
+        if (Object.keys(remainingChannels).length > 0) {
+            eventEnabledByChannel[eventId] = remainingChannels;
+        }
+    });
+    const groupFrequencyByGroupId = {};
+    Object.entries(current.groupFrequencyByGroupId).forEach(([groupId, frequency]) => {
+        if (saved.groupFrequencyByGroupId[groupId] !== frequency) {
+            groupFrequencyByGroupId[groupId] = frequency;
+        }
+    });
+    return { eventEnabledByChannel, groupFrequencyByGroupId };
+};
+const notificationPreferencesView = createSlice({
+    name: 'notificationPreferencesView',
+    initialState,
+    reducers: {
+        clearAllNotificationPreferencesView(draft) {
+            // Reset everything EXCEPT `cancelEpoch`, which must stay monotonic
+            // across the lifetime of the app instance. `initialState.cancelEpoch`
+            // is `0`; returning `initialState` verbatim would rewind the counter
+            // to zero, and any in-flight save whose `cancelEpochAtDispatch` was
+            // captured pre-clearAll (>0) would then satisfy the "captured >=
+            // current" epoch guard and merge stale edits into fresh preferences.
+            // Bumping instead of resetting also invalidates the abandoned save
+            // for free — Cursor Bugbot bc7876f1 followup.
+            const nextCancelEpoch = draft.cancelEpoch + 1;
+            // saveEpoch must also stay monotonic across clearAll for the same
+            // reason (Cursor Bugbot 3632510237). Rewinding to 0 would let a
+            // stale-in-flight GET whose `saveEpochAtDispatch` was captured >0
+            // satisfy the "captured >= current" epoch guard and clobber fresh
+            // preferences on any subsequent save.
+            const nextSaveEpoch = draft.saveEpoch + 1;
+            return {
+                ...initialState,
+                cancelEpoch: nextCancelEpoch,
+                saveEpoch: nextSaveEpoch,
+            };
+        },
+        clearNotificationPreferencesLocalOverrides(draft) {
+            // Discards in-flight per-event/per-group edits held in `localOverrides`
+            // without touching the fetched `preferences` snapshot. Used by the
+            // settings-page Cancel affordance so the effective preferences revert
+            // to the last server-known state without triggering a refetch race.
+            //
+            // Cancel/in-flight-save race: every Cancel bumps `cancelEpoch`
+            // monotonically. Any save that captured a lower epoch value at
+            // dispatch time is treated as stale by the Success/Failure reducer
+            // — its merge is skipped. Unconditional bump (vs the earlier
+            // counter model) survives switchMap abandonment and double-Cancel
+            // (Cursor Bugbot 4aa021f7): even if the abandoned save's
+            // Success/Failure never dispatches, subsequent legitimate saves
+            // still work because their captured epoch matches the current one.
+            draft.cancelEpoch += 1;
+            draft.localOverrides = emptyNotificationPreferences();
+            // Also drop `savePreferencesState` back to Not-Started so any
+            // "Saving…" affordance bound to `getNotificationPreferencesSaveState`
+            // clears on Cancel. Without this, a Cancel-during-save whose stale
+            // Success/Failure never fires (switchMap abandonment) leaves the
+            // selector reporting In-Progress forever — Cursor Bugbot bc7876f1.
+            draft.savePreferencesState = { fetchState: 'Not-Started' };
+        },
+        fetchNotificationPreferencesSuccess(draft, action) {
+            // Piggybacks on the settings-envelope fetch. The GET response is a full
+            // snapshot of the server-known preferences (empty maps included), so
+            // REPLACE `preferences` rather than merging — merging would leak keys
+            // the server has since removed. DO NOT touch `localOverrides`: a refetch
+            // that fires while the user has in-flight edits (pre-debounce) must not
+            // silently drop them; the save-success path is the only clearer.
+            // A `null`/`undefined` payload isn't a snapshot at all (e.g. the
+            // envelope key was omitted); no-op instead of wiping preferences.
+            if (action.payload.preferences == null) {
+                return;
+            }
+            // Stale-GET guard (Cursor Bugbot 3632510237): if the fetch epic
+            // captured a `saveEpoch` lower than the current one, a save has
+            // succeeded since this GET dispatched — the response is carrying
+            // the pre-PUT snapshot and would clobber the just-saved server
+            // truth back to the pre-edit state until the next refetch. Skip
+            // the replace; the store already reflects the fresher save.
+            if (action.payload.saveEpochAtDispatch < draft.saveEpoch) {
+                return;
+            }
+            draft.preferences = mapPayloadToPreferences(action.payload.preferences);
+        },
+        saveNotificationPreferences(draft) {
+            draft.savePreferencesState = { fetchState: 'In-Progress' };
+        },
+        saveNotificationPreferencesFailure(draft, action) {
+            // Stale failure from a cancelled-since save — swallow silently so
+            // the UI doesn't surface an error banner for a save the user
+            // already abandoned.
+            if (action.payload.cancelEpochAtDispatch < draft.cancelEpoch) {
+                return;
+            }
+            // Preserve `localOverrides` so the user's in-flight edits survive a
+            // transient network blip. UI should surface an error affordance and
+            // allow retry.
+            draft.savePreferencesState = {
+                fetchState: 'Error',
+                error: action.payload.error,
+            };
+        },
+        saveNotificationPreferencesSuccess(draft, action) {
+            // Preserve-on-partial: PUT /preferences is patch-semantic. The response
+            // echoes only the fields that changed, so merge into `preferences`
+            // instead of replacing — otherwise a single-channel toggle would wipe
+            // every other stored preference.
+            //
+            // Rollback invariant (F5): `serverEcho` may be `undefined` if the server
+            // rolls back to an older shape that omits the echo entirely. In that
+            // case fall back to merging `savedOverrides` into `preferences` — the
+            // PUT succeeded (2xx), so the values we sent are now server truth. If
+            // we merged an empty patch instead, `subtractSavedOverrides` would
+            // still strip the just-saved keys from `localOverrides`, leaving the
+            // effective preferences (preferences ∪ localOverrides) reverted to the
+            // pre-edit server snapshot until the next refetch.
+            //
+            // In-flight-edit invariant: `savedOverrides` is the exact snapshot the
+            // epic PUT to the server. Subtracting those keys from `localOverrides`
+            // (instead of clearing it wholesale) preserves any edits the user
+            // added AFTER the debounce fired but BEFORE the response landed. The
+            // next debounce cycle will pick them up. Clearing wholesale drops
+            // in-flight edits from both UI (once server echo lands) and server.
+            // Cancel/in-flight-save race: `cancelEpoch` monotonically increases
+            // on every Cancel. If the save captured a lower epoch at dispatch,
+            // the user has pressed Cancel since — skip the `preferences` merge
+            // and the `localOverrides` subtract (Cancel already emptied it).
+            // Do NOT flip fetchState so a subsequent legit save can still show
+            // its own In-Progress → Completed lifecycle. The server itself has
+            // accepted the write — reverting server-side is out of FE scope; UI
+            // reflects the cancelled intention until the next refetch merges
+            // whatever the server persisted.
+            if (action.payload.cancelEpochAtDispatch < draft.cancelEpoch) {
+                return;
+            }
+            // Bump `saveEpoch` so any settings-envelope GET that was in flight
+            // BEFORE this PUT resolved is treated as stale. Its captured epoch
+            // will be lower than the new value, so its reducer branch will
+            // skip the `preferences` replace. Cursor Bugbot 3632510237.
+            draft.saveEpoch += 1;
+            draft.savePreferencesState = { fetchState: 'Completed' };
+            const patch = action.payload.serverEcho == null
+                ? action.payload.savedOverrides
+                : mapPayloadToPreferences(action.payload.serverEcho);
+            draft.preferences = mergePreferences(draft.preferences, patch);
+            draft.localOverrides = subtractSavedOverrides(draft.localOverrides, action.payload.savedOverrides);
+        },
+        setGroupFrequency(draft, action) {
+            draft.localOverrides.groupFrequencyByGroupId[action.payload.groupId] =
+                action.payload.frequency;
+        },
+        toggleEventChannel(draft, action) {
+            const { channel, enabled, eventId } = action.payload;
+            const eventMap = {
+                ...(draft.localOverrides.eventEnabledByChannel[eventId] ?? {}),
+            };
+            eventMap[channel] = enabled;
+            draft.localOverrides.eventEnabledByChannel[eventId] = eventMap;
+        },
+    },
+});
+export const { clearAllNotificationPreferencesView, clearNotificationPreferencesLocalOverrides, fetchNotificationPreferencesSuccess, saveNotificationPreferences, saveNotificationPreferencesFailure, saveNotificationPreferencesSuccess, setGroupFrequency, toggleEventChannel, } = notificationPreferencesView.actions;
+export default notificationPreferencesView.reducer;

package/lib/esm/view/notificationPreferencesView/notificationPreferencesViewSelector.js

@@ -0,0 +1,25 @@
+const getView = (state) => state.notificationPreferencesViewState;
+export const getNotificationPreferencesSaveState = (state) => getView(state).savePreferencesState;
+export const getEffectiveNotificationPreferences = (state) => {
+    const view = getView(state);
+    const mergedEventEnabledByChannel = { ...view.preferences.eventEnabledByChannel };
+    Object.entries(view.localOverrides.eventEnabledByChannel).forEach(([eventId, channels]) => {
+        mergedEventEnabledByChannel[eventId] = {
+            ...(view.preferences.eventEnabledByChannel[eventId] ?? {}),
+            ...channels,
+        };
+    });
+    return {
+        eventEnabledByChannel: mergedEventEnabledByChannel,
+        groupFrequencyByGroupId: {
+            ...view.preferences.groupFrequencyByGroupId,
+            ...view.localOverrides.groupFrequencyByGroupId,
+        },
+    };
+};
+export const getNotificationLocalOverrides = (state) => getView(state).localOverrides;
+export const hasUnsavedNotificationPreferences = (state) => {
+    const overrides = getView(state).localOverrides;
+    return (Object.keys(overrides.eventEnabledByChannel).length > 0 ||
+        Object.keys(overrides.groupFrequencyByGroupId).length > 0);
+};

package/lib/esm/view/notificationPreferencesView/notificationPreferencesViewState.js

@@ -0,0 +1,4 @@
+export const emptyNotificationPreferences = () => ({
+    eventEnabledByChannel: {},
+    groupFrequencyByGroupId: {},
+});

package/lib/esm/view/onboardingView/cockpitView/epic/initializeOnboardingCustomerViewUpdateDataEpic.js

@@ -122,11 +122,7 @@ const getSelectedProducts = (isDebitCardFlagEnabled, tenant) => {
         return [];
     }
     else if (isBookkeepingEnabled) {
-        return [
-            'bookkeeping',
-            'zeni_bill_pay',
-            'zeni_reimbursements',
-        ];
+        return ['bookkeeping', 'zeni_bill_pay', 'zeni_reimbursements'];
     }
     else if (isOtherProductsEnabled) {
         const selectedProducts = [];

package/lib/esm/view/onboardingView/customerView/epic/customerDetails/updateOnboardingCustomerViewLocalStoreDataEpic.js

@@ -78,9 +78,8 @@ export const updateOnboardingCustomerViewLocalStoreDataEpic = (actions$, state$)
                 companyView?.company.company.companyOnboardingInfo
                     .subscriptionBillingAddressId != null) {
                 updatedCurrentStep = 'connect_ledger';
-                const isOnboardingAiActivationViewed = companyOnboardingInfo?.onboardingInfo
-                    ?.onboardingAiActivationInfo?.isOnboardingAiActivationViewed ??
-                    false;
+                const isOnboardingAiActivationViewed = companyOnboardingInfo?.onboardingInfo?.onboardingAiActivationInfo
+                    ?.isOnboardingAiActivationViewed ?? false;
                 // Past the ledger step we always sit on connect_data_source —
                 // it has many integrations, so we treat it as never auto-complete
                 // and only advance to verification on an explicit user dispatch.
@@ -114,7 +113,9 @@ export const updateOnboardingCustomerViewLocalStoreDataEpic = (actions$, state$)
             // stale subStep (e.g. 'default' carried over from another step)
             // leaves verification rendering an empty form.
             if (updatedCurrentStep !== onboardingCustomerViewState.currentStep) {
-                const targetSubStep = updatedCurrentStep === 'verification' ? 'unlock-stack' : 'default';
+                const targetSubStep = updatedCurrentStep === 'verification'
+                    ? 'unlock-stack'
+                    : 'default';
                 fetchActions.push(updateCurrentSubStep({ subStep: targetSubStep }));
             }
         }

package/lib/esm/view/recommendation/fetchEntityRecommendationsForLineUpdateEpic.js

@@ -37,7 +37,7 @@ const toGroupKey = (flowType, transactionId, lineIds) => `${flowType}${SEPARATOR
 export const fetchEntityRecommendationsForLineUpdateEpic = (actions$, state$, zeniAPI) => actions$.pipe(filter(fetchEntityRecommendationsForLineUpdate.match), groupBy((action) => toGroupKey(action.payload.flowType, action.payload.transactionDetails.transactionId.id, action.payload.transactionDetails.lineIds), undefined, (group$) => group$.pipe(debounce(() => timer(GROUP_INACTIVITY_TIMEOUT_MS)))), mergeMap((group$) => group$.pipe(switchMap((action) => {
     const payload = action.payload;
     const { transactionId, transaction, lineIds } = payload.transactionDetails;
-    const { entity, amount, isFetchCOT, } = payload;
+    const { entity, amount, isFetchCOT } = payload;
     // The vendor "Update all lines" popup on the detail page watches
     // its own transaction-level fetch status, separate from the
     // per-line statuses below — surface completion/failure there too

package/lib/esm/view/settingsView/epic/fetchNotificationSettingsEpic.js

@@ -1,19 +1,51 @@
 import { from, of } from 'rxjs';
 import { catchError, filter, mergeMap, switchMap } from 'rxjs/operators';
+import { updateNotificationRegistry } from '../../../entity/notificationRegistry/notificationRegistryReducer';
 import { createZeniAPIStatus, isSuccessResponse } from '../../../responsePayload';
+import { notificationPreferencesUrl } from '../../notificationPreferencesView/notificationPreferencesEndpoint';
+import { fetchNotificationPreferencesSuccess } from '../../notificationPreferencesView/notificationPreferencesViewReducer';
 import { fetchNotificationSettings, updateNotificationSettingsOnFailure, updateNotificationSettingsOnSuccess, } from '../settingsViewReducer';
 export const fetchNotificationSettingsEpic = (actions$, state$, zeniAPI) => actions$.pipe(filter(fetchNotificationSettings.match), switchMap(() => {
     const state = state$.value;
-    const URL = `${zeniAPI.apiEndPoints.notificationMicroServiceBaseUrl}/1.0/notification-preferences`;
     const userEmail = state.tenantState.loggedInUser?.userEmail;
     if (userEmail == null) {
         return from([]);
     }
-    return zeniAPI.getJSON(URL).pipe(mergeMap((response) => {
+    // Snapshot the save epoch at GET-dispatch time. The reducer compares
+    // the captured value against the current `saveEpoch` on response and
+    // skips the `preferences` replace when a save has landed in the
+    // meantime — the GET is carrying the pre-PUT snapshot and would
+    // otherwise clobber the fresh save. Cursor Bugbot 3632510237.
+    const saveEpochAtDispatch = state.notificationPreferencesViewState.saveEpoch;
+    // Snapshot the registry clear epoch at GET-dispatch time (same idiom as
+    // `saveEpochAtDispatch` above). The registry reducer compares it against
+    // the current `registryEpoch` and skips its write when a
+    // `clearAllNotificationRegistry` (tenant switch) has landed since — the
+    // GET is carrying the prior tenant's snapshot. Cursor Bugbot 67d6918e.
+    const registryEpochAtDispatch = state.notificationRegistryState.registryEpoch;
+    return zeniAPI
+        .getJSON(notificationPreferencesUrl(zeniAPI))
+        .pipe(mergeMap((response) => {
         if (isSuccessResponse(response) && response.data != null) {
             const updateActions = [
                 updateNotificationSettingsOnSuccess(response.data, userEmail),
             ];
+            // Always dispatch — an absent `task_checklist_registry` (gate
+            // off) must CLEAR the prior tenant's registry, not leave it in
+            // place. The reducer clears on `undefined` and full-replaces
+            // otherwise, both guarded by the registry epoch so a stale GET
+            // that lands after a tenant switch is skipped. Cursor Bugbot
+            // 67d6918e.
+            updateActions.push(updateNotificationRegistry({
+                registry: response.data.task_checklist_registry ?? undefined,
+                registryEpochAtDispatch,
+            }));
+            if (response.data.task_checklist_preferences != null) {
+                updateActions.push(fetchNotificationPreferencesSuccess({
+                    preferences: response.data.task_checklist_preferences,
+                    saveEpochAtDispatch,
+                }));
+            }
             return of(...updateActions);
         }
         else {

package/lib/esm/view/settingsView/epic/saveNotificationSettingsEpic.js

@@ -2,9 +2,10 @@ import { of } from 'rxjs';
 import { catchError, filter, mergeMap, switchMap } from 'rxjs/operators';
 import { openSnackbar } from '../../../entity/snackbar/snackbarReducer';
 import { createZeniAPIStatus, isSuccessResponse } from '../../../responsePayload';
+import { notificationPreferencesUrl } from '../../notificationPreferencesView/notificationPreferencesEndpoint';
 import { saveNotificationSettings, updateNotificationSettingsOnSaveFailure, updateNotificationSettingsOnSaveSuccess, } from '../settingsViewReducer';
 export const saveNotificationSettingsEpic = (actions$, state$, zeniAPI) => actions$.pipe(filter(saveNotificationSettings.match), switchMap(() => {
-    const URL = `${zeniAPI.apiEndPoints.notificationMicroServiceBaseUrl}/1.0/notification-preferences`;
+    const URL = notificationPreferencesUrl(zeniAPI);
     const { notificationSettings, notificationSettingsLocalData } = state$.value.settingsViewState.notification;
     const payload = toSaveNotificationSettingsPayload(notificationSettingsLocalData, notificationSettings);
     return zeniAPI

package/lib/esm/view/settingsView/settingsViewHelpers.js

@@ -145,13 +145,14 @@ export const isMonthEndNotificationsSectionVisibleOnSettingsPage = (monthEndInsi
     return (monthEndInsightsNotificationSettings.enabled != null ||
         monthEndInsightsNotificationSettings.recipientEmailIds.includes(signedInUseEmail));
 };
-export const isNotificationsTabVisible = (notificationSettings, signedInUseEmail, isDebitCardFlagEnabled, currentTenant) => {
+export const isNotificationsTabVisible = (notificationSettings, signedInUseEmail, isDebitCardFlagEnabled, currentTenant, hasTaskChecklistAccess) => {
     if (currentTenant == null) {
         return false;
     }
     const { reminderNotificationSettings, monthEndInsightsNotificationSettings } = notificationSettings;
     return ((isRemindersSectionVisibleOnSettingsPage(reminderNotificationSettings) ||
-        isMonthEndNotificationsSectionVisibleOnSettingsPage(monthEndInsightsNotificationSettings, signedInUseEmail)) &&
+        isMonthEndNotificationsSectionVisibleOnSettingsPage(monthEndInsightsNotificationSettings, signedInUseEmail) ||
+        hasTaskChecklistAccess) &&
         (isTenantAccountingServicesEnabled(currentTenant) ||
             (isTenantBankingOnly(isDebitCardFlagEnabled, currentTenant) === false &&
                 isTenantCardsOnly(currentTenant) === false)));

package/lib/esm/view/spendManagement/commonSetup/setupViewReducer.js

@@ -111,7 +111,8 @@ const setupView = createSlice({
         saveSetupViewDataInLocalStore(draft, action) {
             const setupViewLocalData = action.payload;
             if (setupViewLocalData.companyDetails != null) {
-                const syncToken = setupViewLocalData.companyDetails.syncToken ?? draft.companyDetails.localData?.syncToken;
+                const syncToken = setupViewLocalData.companyDetails.syncToken ??
+                    draft.companyDetails.localData?.syncToken;
                 draft.companyDetails.localData = {
                     ...setupViewLocalData.companyDetails,
                     ...(syncToken != null ? { syncToken } : {}),

package/lib/esm/view/transactionDetail/epics/saveTransactionDetailEpic.js

@@ -1,8 +1,8 @@
 import recordGet from 'lodash/get';
 import { from } from 'rxjs';
 import { filter, mergeMap } from 'rxjs/operators';
-import { getSupportedTransactionById } from '../../../entity/transaction/transactionSelector';
 import { getIsAccountingProjectsEnabled } from '../../../entity/tenant/tenantSelector';
+import { getSupportedTransactionById } from '../../../entity/transaction/transactionSelector';
 import { saveTransactionDetail, updateTransactionDetail, } from '../transactionDetailReducer';
 import { getTransactionDetailKey } from '../transactionDetailState';
 import { toTransactionUpdatesFromTransactionDetailLocalData } from './saveTransactionHelper';

package/lib/esm/view/transactionDetail/epics/updateTransactionDetailEpic.js

@@ -29,7 +29,7 @@ import { getTransactionDetailKey, } from '../transactionDetailState';
 export const updateTransactionDetailEpic = (actions$, state$, zeniAPI) => actions$.pipe(filter(updateTransactionDetail.match), mergeMap((action) => {
     const { transactionState, vendorState, transactionDetailState } = state$.value;
     const isAccountingProjectsEnabled = getIsAccountingProjectsEnabled(state$.value);
-    const { cotTransactionTracking, transactionId, transactionSaveUpdates, } = action.payload;
+    const { cotTransactionTracking, transactionId, transactionSaveUpdates } = action.payload;
     return zeniAPI
         .putAndGetJSON(`${zeniAPI.apiEndPoints.accountMicroServiceBaseUrl}/1.0/transactions/${action.payload.transactionId.id}/categorize`, preparePayload(transactionState, vendorState, transactionDetailState, transactionId, transactionSaveUpdates, cotTransactionTracking, isAccountingProjectsEnabled))
         .pipe(mergeMap((response) => {