@rapidmx/web-client 0.4.0 → 0.5.0

package/apps/shared/mail/listAllPages.ts

@@ -0,0 +1,39 @@
+///////////////////////////////////////////////////////////////////////////////
+// Copyright (C) 2026 Jean-Philippe Steinmetz
+// SPDX-License-Identifier: MPL-2.0
+///////////////////////////////////////////////////////////////////////////////
+
+/** Page size the list pages (Contacts, Tasks) request per call - restapi caps `limit` at 500. */
+export const LIST_PAGE_SIZE = 500;
+
+/** Safety cap on pages fetched - stops a server that ignores `page` (and keeps returning a full first
+ * page) from looping forever. 40 pages x 500 = 20,000 items. */
+export const MAX_LIST_PAGES = 40;
+
+export interface ListAllPagesResult<T> {
+    items: T[];
+    /** `true` when fetching stopped at `maxPages` with the last page still full - there may be more items
+     * the caller isn't showing, so it should say so rather than presenting `items` as the whole list. */
+    truncated: boolean;
+}
+
+/**
+ * Fetches every page of a zero-based `limit`/`page` list endpoint, stopping at the first short page
+ * (fewer than `pageSize` items) - so a folder with more items than one page holds is shown in full
+ * rather than silently cut off at the first page. Stops at `maxPages` regardless, reporting `truncated`.
+ */
+export async function listAllPages<T>(
+    fetchPage: (page: number) => Promise<T[]>,
+    pageSize: number = LIST_PAGE_SIZE,
+    maxPages: number = MAX_LIST_PAGES,
+): Promise<ListAllPagesResult<T>> {
+    const items: T[] = [];
+    for (let page = 0; page < maxPages; page++) {
+        const batch = await fetchPage(page);
+        items.push(...batch);
+        if (batch.length < pageSize) {
+            return { items, truncated: false };
+        }
+    }
+    return { items, truncated: true };
+}

package/apps/shared/search/LocalIndexLifecycle.tsx

@@ -3,87 +3,96 @@
 // SPDX-License-Identifier: MPL-2.0
 ///////////////////////////////////////////////////////////////////////////////
 /**
- * Mounts the Tier 2 local index's lifecycle for one mailbox: starts the background build once it's
- * unlocked, and destroys the index on the same events that destroy the unlocked keys themselves (spec
- * §11 "MUST be destroyed on the same events that destroy private keys: explicit logout, session
- * revocation, and the configurable idle timeout").
+ * Mounts the Tier 2 local index's lifecycle: starts the background build for the active mailbox once it's
+ * unlocked, and destroys an index on the same events that destroy that mailbox's unlocked keys (spec §11
+ * "MUST be destroyed on the same events that destroy private keys: explicit logout, session revocation,
+ * and the configurable idle timeout").
  *
  * **Why polling, not hooking the existing destroy call sites directly**: `destroyUnlockedKeys()`
- * (`react-shared/src/crypto/keySession.ts`) has no observer/callback hook, and its own two real call
- * sites are `useIdleKeyTimeout.ts` (in `react-shared`, not this repo) and the manual "Destroy keys now"
- * button in Settings - editing the former would mean a react-shared source change that (per this
- * session's own earlier finding) doesn't reach `web-client` without a package republish + patch refresh
- * cycle, which is out of scope for wiring up a destroy signal. Watching `getUnlockedKeys()` for a
- * present-to-absent transition instead catches *every* destroy path uniformly - idle timeout, the manual
+ * (`react-shared/src/crypto/keySession.ts`) has no observer/callback hook. Watching `getUnlockedKeys()`
+ * for a present-to-absent transition catches *every* destroy path uniformly - idle timeout, the manual
  * button, or anything else that calls it - without needing to know which one fired.
  *
- * **Explicit logout is the one gap this polling doesn't reliably cover**: `AppShell.tsx`'s sign-out
- * navigates away immediately, which may not leave time for a poll tick to fire first. That case is
- * handled separately, directly in `AppShell.tsx`, via `destroyAllLocalIndexes()` - see that call site's
- * own comment.
+ * Every mailbox this component has seen unlocked is tracked for the life of the mount - not just whichever
+ * is active right now - so switching mailboxes (or a folders-list refresh re-running the build effect)
+ * can never lose a pending unlocked-to-locked transition for a mailbox whose index was already built.
+ *
+ * **Explicit logout** navigates away immediately, which may not leave time for a poll tick - `AppShell.tsx`
+ * handles that case itself via `destroyAllLocalIndexes()`.
  */
 import { useEffect, useRef } from "react";
 import { getUnlockedKeys } from "@rapidmx/react-shared/crypto/keySession.js";
 import type { PublicKey } from "@rapidmx/react-shared/crypto/keyvaultApi.js";
 import type { Folder } from "@rapidmx/react-shared/mail/mailApi.js";
-import { buildLocalIndex } from "./localIndexBuilder.js";
-import { destroyLocalIndex } from "./localIndexRpcClient.js";
+import { buildLocalIndex, cancelLocalIndexBuild } from "./localIndexBuilder.js";
+import { destroyLocalIndex, pruneInaccessibleLocalIndexes } from "./localIndexRpcClient.js";
 
-const POLL_INTERVAL_MS = 5_000;
+export const POLL_INTERVAL_MS = 5_000;
 
 export interface LocalIndexLifecycleProps {
     mailboxUid?: string;
     mailboxKeys?: PublicKey[];
     folders: Folder[];
+    /** Every mailbox the signed-in user can currently access. Once known, indexes on this device for any
+     * other mailbox (e.g. left behind by a different user who never signed out) are removed. */
+    accessibleMailboxUids?: string[];
 }
 
-/** Renders nothing - pure side-effect component, mounted by `MailShell.tsx` (which is where a
- * `mailboxUid` is actually known; `AppShell.tsx` itself is mailbox-agnostic, shared by every app). Each
- * `buildLocalIndex()` call below omits its `windowConfig` argument deliberately - that leaves the byte
- * budget to its own default, which already resolves per-device (Web vs. Electron) and per-user
- * preference (Settings > Encryption) on its own; see `localIndexBuilder.ts`/`localIndexSizePreference.ts`
- * for how. */
-export default function LocalIndexLifecycle({ mailboxUid, folders }: LocalIndexLifecycleProps) {
-    // Guards against re-triggering a build every time this component re-renders (e.g. on an unrelated
-    // folders-list refresh) for a mailbox already built/building this session.
-    const buildStartedForRef = useRef<string | undefined>(undefined);
-    const wasUnlockedRef = useRef(false);
+/** Renders nothing - pure side-effect component, mounted by `MailShell.tsx`. */
+export default function LocalIndexLifecycle({ mailboxUid, folders, accessibleMailboxUids }: LocalIndexLifecycleProps) {
+    // mailboxUid -> whether it was unlocked at the last check. An entry exists for every mailbox whose
+    // build this component started; only ever changed by a real observed transition, never reset by an
+    // effect re-run.
+    const trackedRef = useRef(new Map<string, boolean>());
+    // The latest props, for the long-lived polling interval below.
+    const latestRef = useRef({ mailboxUid, folders });
+    latestRef.current = { mailboxUid, folders };
 
-    useEffect(() => {
-        if (!mailboxUid || folders.length === 0) {
+    function startBuildIfUnlocked(targetMailboxUid: string, targetFolders: Folder[]) {
+        const unlocked = getUnlockedKeys(targetMailboxUid);
+        if (!unlocked || targetFolders.length === 0 || trackedRef.current.get(targetMailboxUid)) {
             return;
         }
-        const unlocked = getUnlockedKeys(mailboxUid);
-        wasUnlockedRef.current = !!unlocked;
-        if (unlocked && buildStartedForRef.current !== mailboxUid) {
-            buildStartedForRef.current = mailboxUid;
-            // Never an unhandled rejection - a broken local index (Worker/WASM/OPFS unsupported or
-            // unavailable, a corrupted store) is best-effort infrastructure, not a build the rest of the
-            // app depends on. searchTier2.ts's own callers already degrade gracefully independent of
-            // whether a build ever completed at all.
-            buildLocalIndex(mailboxUid, unlocked, folders).catch(() => undefined);
+        trackedRef.current.set(targetMailboxUid, true);
+        // Never an unhandled rejection - a broken local index is best-effort infrastructure, not a build
+        // the rest of the app depends on.
+        buildLocalIndex(targetMailboxUid, unlocked, targetFolders).catch(() => undefined);
+    }
+
+    useEffect(() => {
+        if (mailboxUid) {
+            startBuildIfUnlocked(mailboxUid, folders);
         }
+    }, [mailboxUid, folders]);
 
+    useEffect(() => {
         const interval = setInterval(() => {
-            const stillUnlocked = !!getUnlockedKeys(mailboxUid);
-            if (wasUnlockedRef.current && !stillUnlocked) {
-                // A present-to-absent transition: something just destroyed this mailbox's unlocked keys
-                // (idle timeout or the manual "Destroy keys now" button - see this module's own doc
-                // comment on why this is observed rather than hooked directly).
-                void destroyLocalIndex(mailboxUid);
-                buildStartedForRef.current = undefined;
-            } else if (!wasUnlockedRef.current && stillUnlocked && buildStartedForRef.current !== mailboxUid) {
-                // The mailbox was re-unlocked this session (e.g. via ComposeWindow's or
-                // MessageDetailPane's own on-demand unlock prompt) - start the build it missed the first
-                // time around.
-                buildStartedForRef.current = mailboxUid;
-                buildLocalIndex(mailboxUid, getUnlockedKeys(mailboxUid)!, folders).catch(() => undefined);
+            for (const [trackedUid, wasUnlocked] of trackedRef.current) {
+                if (wasUnlocked && !getUnlockedKeys(trackedUid)) {
+                    // A present-to-absent transition: something just destroyed this mailbox's keys.
+                    trackedRef.current.set(trackedUid, false);
+                    // Stop the pass still running with the now-destroyed keys; the destroy itself also makes
+                    // the Worker reject anything that pass still sends.
+                    void cancelLocalIndexBuild(trackedUid);
+                    void destroyLocalIndex(trackedUid);
+                }
+            }
+            // The active mailbox was (re-)unlocked since the last check, e.g. via an on-demand unlock prompt.
+            const { mailboxUid: activeUid, folders: activeFolders } = latestRef.current;
+            if (activeUid) {
+                startBuildIfUnlocked(activeUid, activeFolders);
             }
-            wasUnlockedRef.current = stillUnlocked;
         }, POLL_INTERVAL_MS);
-
         return () => clearInterval(interval);
-    }, [mailboxUid, folders]);
+    }, []);
+
+    // A stable string key so a re-render with an equal-but-new array doesn't re-scan OPFS.
+    const accessibleKey = accessibleMailboxUids && accessibleMailboxUids.length > 0 ? JSON.stringify([...accessibleMailboxUids].sort()) : "";
+    useEffect(() => {
+        if (accessibleKey) {
+            void pruneInaccessibleLocalIndexes(JSON.parse(accessibleKey) as string[]);
+        }
+    }, [accessibleKey]);
 
     return null;
 }