@naniteninja/dashboard-components-lib 2.4.5 → 2.4.6

package/index.d.ts

@@ -1860,6 +1860,10 @@ interface ISwipeableTabsHost {
     mainSwiperInstance: Swiper__default;
     _activeIndex: number;
     activeIndex: number;
+    mainSwiperGestureActive: boolean;
+    mainSwiperLastGestureAt: number;
+    activeIndexBeforeLastEmit: number;
+    lastActiveIndexEmitAt: number;
     enableGrouping: boolean;
     enableDragAndDrop: boolean;
     enableTabBarScrollDrag: boolean;
@@ -1982,6 +1986,7 @@ interface ISwipeableTabsHost {
     mergeNewItemsAfterRestore(storedRule: StoredRule): void;
     updateDisplayItems(): void;
     saveState(): void;
+    schedulePortalStabilize?(): void;
 }
 
 declare class SwipeableTabsResizeService {
@@ -2183,6 +2188,30 @@ declare class SwipeableTabsHostState {
     expandedItemLeft: number;
     expandedItemRef: ILibClientMatchOverview | null;
     _activeIndex: number;
+    /**
+     * The main swiper's `slideChange` is only honoured while the user is actually dragging it (or
+     * shortly after they let go / pressed an arrow key). Swiper also fires `slideChange` on its own
+     * after `update()` recomputes the active slide from the translate — and `update()` runs on every
+     * DOM mutation because the swiper is created with `observer: true`. On the client dashboard the
+     * content swiper sits squashed behind a 55px belt, so those recomputations could land on a
+     * neighbouring slide and drag the expanded prospect along with them, one tab at a time, with
+     * nobody touching anything. Without a gesture there is nothing to follow.
+     */
+    mainSwiperGestureActive: boolean;
+    mainSwiperLastGestureAt: number;
+    /**
+     * What `_activeIndex` was right before this component last announced a new index, and when.
+     *
+     * Hosts feed `activeIndexChange` back into `[activeIndex]`, sometimes after a delay and via
+     * config objects that get rebuilt on every data refresh. A rebuild that happens between our emit
+     * and the host catching up pushes the *old* index straight back in, which used to re-expand the
+     * previous prospect and then flip forward again when the host finally caught up. An incoming
+     * value that equals the index we just moved away from, within a short window, is that echo and
+     * is ignored — a genuine host request to go back to it inside that window cannot be told apart,
+     * and is not something a person can do within 1.5 seconds of tapping a different tab.
+     */
+    activeIndexBeforeLastEmit: number;
+    lastActiveIndexEmitAt: number;
 }
 
 declare class SwipeableTabsStateService {
@@ -3292,6 +3321,20 @@ declare class ClientViewportSlidesService {
     handleProfileEdgeDrag(event: 'left' | 'right' | Event): void;
     handleHandoffSwipeNext(): void;
     handleHandoffSwipePrev(): void;
+    /**
+     * A different prospect tab was chosen.
+     *
+     * The state moves immediately: config index, expanded flags, the host's `activeIndexChange`.
+     * Only the slide-out / slide-in of the content panel is timed. This used to all sit inside the
+     * 150ms slide-out delay, which left the host holding the previous index while data refreshes
+     * kept rebuilding its config — each rebuild pushed that previous index back into the belt and
+     * re-expanded the prospect the user had just left, until the delayed emit flipped it forward
+     * again. With the host told at once there is no window for that.
+     *
+     * The matches are no longer re-emitted here. Flipping `isExpanded` in place is all the belt and
+     * the spider chart read; pushing a fresh array through `clientMatches$` on every tab change only
+     * made every subscriber — including the belt itself — re-run its refresh logic for no new data.
+     */
     onChatHeadChange(index: number, profileSwiperEl?: ElementRef, previousProspectIndex?: number): number;
     onSwipeStart(event: MouseEvent | TouchEvent): {
         touchStartX: number;
@@ -3323,6 +3366,8 @@ declare class ClientViewportStateService {
     destroy(): void;
     initialize(): void;
     handleConfigChange(): void;
+    /** The Chat Handoff panel shows the active prospect's conversation; call after the matches change. */
+    refreshHandoffForActiveProspect(): void;
     handleClientHomeConfigChange(): void;
     initPageRouting(): void;
     applyActivePageInput(): void;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@naniteninja/dashboard-components-lib",
-  "version": "2.4.5",
+  "version": "2.4.6",
   "author": "naniteninja",
   "repository": {
     "type": "git"