@remit/web-client 0.0.325 → 0.0.327

package/src/hooks/useToggleStar.ts

@@ -1,164 +0,0 @@
-import {
-	messageOperationsUpdateMessageFlagsMutation,
-	threadDetailOperationsListThreadMessagesQueryKey,
-} from "@remit/api-http-client/@tanstack/react-query.gen.ts";
-import type { RemitImapThreadMessageResponse } from "@remit/api-http-client/types.gen.ts";
-import { useMutation, useQueryClient } from "@tanstack/react-query";
-import { useErrorBanners } from "@/components/ui/ErrorBannerProvider";
-import { formatErrorDetail } from "@/components/ui/error-banners";
-import { patchThreadListCache } from "@/lib/thread-cache";
-import {
-	cancelThreadListQueries,
-	invalidateThreadListQueries,
-	patchThreadListQueries,
-	restoreThreadListQueries,
-	snapshotThreadListQueries,
-	type ThreadMessagesData,
-	type ThreadMutationContext,
-	threadListCacheKeys,
-} from "@/lib/thread-list-cache";
-
-interface UseToggleStarOptions {
-	threadId: string;
-	/**
-	 * The mailbox whose lists to patch when the starred message is not in
-	 * `messages` — the browsed mailbox, which is where a list row lives.
-	 */
-	mailboxId: string;
-	/**
-	 * The thread's messages, when the caller has them. A conversation spans
-	 * mailboxes (#46), so the lists to patch are the ones for the mailbox the
-	 * starred message is actually in, not the one being browsed.
-	 */
-	messages?: RemitImapThreadMessageResponse[];
-}
-
-/**
- * The mailbox whose cached listings a mutation on `messageId` affects.
- *
- * The message's own mailbox, falling back to the browsed one when the thread's
- * messages are unknown or do not contain it. Starring a reply in Sent from a
- * conversation opened in INBOX has to patch Sent's lists; INBOX's do not hold
- * that message and patching them changes nothing.
- */
-export const resolveMailboxForMessage = (
-	messageId: string,
-	messages: RemitImapThreadMessageResponse[] | undefined,
-	fallbackMailboxId: string,
-): string =>
-	messages?.find((message) => message.messageId === messageId)?.mailboxId ??
-	fallbackMailboxId;
-
-export const toggleStarsInItems = (
-	items: RemitImapThreadMessageResponse[],
-	messageId: string,
-	nextStarred: boolean,
-): RemitImapThreadMessageResponse[] =>
-	items.map((item) =>
-		item.messageId === messageId ? { ...item, hasStars: nextStarred } : item,
-	);
-
-export const useToggleStar = ({
-	threadId,
-	mailboxId,
-	messages,
-}: UseToggleStarOptions) => {
-	const queryClient = useQueryClient();
-	const { pushError } = useErrorBanners();
-
-	const { mutate, isPending, variables } = useMutation({
-		...messageOperationsUpdateMessageFlagsMutation(),
-		onMutate: async (vars): Promise<ThreadMutationContext> => {
-			const messageId = vars.path.messageId;
-			const nextStarred = vars.body.isStarred ?? false;
-
-			// Use partial-key prefixes so the cancel/snapshot/patch covers the
-			// full key (which includes query options like { order: "desc",
-			// mailboxId }) without us having to enumerate every variant. React
-			// Query matches by prefix on the first key element.
-			const threadMessagesPrefix =
-				threadDetailOperationsListThreadMessagesQueryKey({
-					path: { threadId },
-				});
-			// The list caches to patch: the message's own mailbox plus the unified
-			// cross-account listing that backs the daily brief and the Flagged view.
-			// Resolved from the shared source so this hook can never fall behind the
-			// others on which listings exist (#149).
-			const listPrefixes = threadListCacheKeys([
-				resolveMailboxForMessage(messageId, messages, mailboxId),
-			]);
-
-			await Promise.all([
-				queryClient.cancelQueries({ queryKey: threadMessagesPrefix }),
-				cancelThreadListQueries(queryClient, listPrefixes),
-			]);
-
-			const previousThreadMessages = queryClient
-				.getQueriesData<ThreadMessagesData>({ queryKey: threadMessagesPrefix })
-				.filter(
-					(entry): entry is [readonly unknown[], ThreadMessagesData] =>
-						entry[1] !== undefined,
-				)
-				.map(([queryKey, data]) => ({ queryKey, data }));
-
-			const previousThreadsList = snapshotThreadListQueries(
-				queryClient,
-				listPrefixes,
-			);
-
-			// The thread-detail cache carries the `{ items }` shape too, so it goes
-			// through the same shape-tolerant helper as the listings.
-			queryClient.setQueriesData({ queryKey: threadMessagesPrefix }, (old) =>
-				patchThreadListCache(old, (items) =>
-					toggleStarsInItems(items, messageId, nextStarred),
-				),
-			);
-			patchThreadListQueries(queryClient, listPrefixes, (items) =>
-				toggleStarsInItems(items, messageId, nextStarred),
-			);
-
-			return {
-				threadMessagesPrefix,
-				listPrefixes,
-				previousThreadMessages,
-				previousThreadsList,
-			};
-		},
-		onError: (err, vars, context) => {
-			if (context) {
-				for (const entry of context.previousThreadMessages) {
-					queryClient.setQueryData(entry.queryKey, entry.data);
-				}
-				restoreThreadListQueries(queryClient, context.previousThreadsList);
-			}
-			const nextStarred = vars.body.isStarred ?? false;
-			pushError({
-				title: nextStarred
-					? "Couldn't star message"
-					: "Couldn't unstar message",
-				detail: formatErrorDetail(err),
-				error: err,
-			});
-		},
-		onSettled: (_data, _err, _vars, context) => {
-			if (!context) return;
-			queryClient.invalidateQueries({ queryKey: context.threadMessagesPrefix });
-			invalidateThreadListQueries(queryClient, context.listPrefixes);
-		},
-	});
-
-	const toggleStar = (messageId: string, currentlyStarred: boolean) => {
-		mutate({
-			path: { messageId },
-			body: {
-				isStarred: !currentlyStarred,
-			},
-		});
-	};
-
-	return {
-		toggleStar,
-		isPending,
-		pendingMessageId: isPending ? variables?.path.messageId : undefined,
-	};
-};

package/src/hooks/useToggleTrusted.test.ts

@@ -1,106 +0,0 @@
-import assert from "node:assert/strict";
-import { describe, test } from "node:test";
-import type {
-	RemitImapDescribeMessageResponse,
-	RemitImapEnvelopeAddressResponse,
-} from "@remit/api-http-client/types.gen.ts";
-import { patchDescribeMessage, patchEnvelopeAddress } from "./useToggleTrusted";
-
-const NOW = 1_700_000_000_000;
-
-const makeAddr = (
-	overrides: Partial<RemitImapEnvelopeAddressResponse> & {
-		addressId: string;
-	},
-): RemitImapEnvelopeAddressResponse =>
-	({
-		normalizedEmail: "x@example.com",
-		addressRole: "from",
-		addressOrder: 0,
-		...overrides,
-	}) as RemitImapEnvelopeAddressResponse;
-
-describe("patchEnvelopeAddress", () => {
-	test("ignores addresses with non-matching addressId", () => {
-		const addr = makeAddr({ addressId: "addr-other" });
-		const result = patchEnvelopeAddress(addr, "addr-target", true, NOW);
-		assert.equal(result, addr);
-	});
-
-	test("sets trusted flag when toggled on", () => {
-		const addr = makeAddr({ addressId: "addr-1" });
-		const result = patchEnvelopeAddress(addr, "addr-1", true, NOW);
-		assert.equal(result.flags?.trusted?.value, true);
-		assert.equal(result.flags?.trusted?.setAt, NOW);
-	});
-
-	test("removes trusted flag when toggled off", () => {
-		const addr = makeAddr({
-			addressId: "addr-1",
-			flags: { trusted: { value: true, setAt: 1 } },
-		});
-		const result = patchEnvelopeAddress(addr, "addr-1", false, NOW);
-		assert.equal(result.flags?.trusted, undefined);
-	});
-
-	test("preserves other flags when toggling trust off", () => {
-		const addr = makeAddr({
-			addressId: "addr-1",
-			flags: {
-				trusted: { value: true, setAt: 1 },
-				vip: { value: true, setAt: 2 },
-			},
-		});
-		const result = patchEnvelopeAddress(addr, "addr-1", false, NOW);
-		assert.equal(result.flags?.vip?.value, true);
-		assert.equal(result.flags?.trusted, undefined);
-	});
-});
-
-describe("patchDescribeMessage", () => {
-	const baseDescribe = (
-		from: RemitImapEnvelopeAddressResponse[],
-	): RemitImapDescribeMessageResponse =>
-		({
-			message: {
-				messageId: "m",
-				mailboxId: "mb",
-				uid: 1,
-				rfc822Size: 1,
-				internalDate: 1,
-				status: "active",
-				syncStatus: "pending",
-				abandonedMutation: "none",
-			},
-			envelope: {
-				messageId: "m",
-				date: 1,
-				from,
-				to: [],
-				cc: [],
-				bcc: [],
-				replyTo: [],
-				category: "uncategorized",
-				senderTrust: "unknown",
-			},
-			flags: [],
-			bodyParts: [],
-			references: [],
-		}) as RemitImapDescribeMessageResponse;
-
-	test("flips only the matching address across all roles", () => {
-		const target = makeAddr({ addressId: "a-1" });
-		const other = makeAddr({ addressId: "a-2" });
-		const data = baseDescribe([target, other]);
-		const result = patchDescribeMessage(data, "a-1", true, NOW);
-		assert.equal(result.envelope.from[0].flags?.trusted?.value, true);
-		assert.equal(result.envelope.from[1].flags?.trusted, undefined);
-	});
-
-	test("rollback semantics: original data is unchanged (immutable patch)", () => {
-		const target = makeAddr({ addressId: "a-1" });
-		const data = baseDescribe([target]);
-		patchDescribeMessage(data, "a-1", true, NOW);
-		assert.equal(data.envelope.from[0].flags, undefined);
-	});
-});

package/src/hooks/useToggleTrusted.ts

@@ -1,157 +0,0 @@
-import {
-	addressDetailOperationsUpdateAddressMutation,
-	messageOperationsDescribeMessageQueryKey,
-} from "@remit/api-http-client/@tanstack/react-query.gen.ts";
-import type {
-	RemitImapAddressFlags,
-	RemitImapDescribeMessageResponse,
-	RemitImapEnvelopeAddressResponse,
-	RemitImapTrustedFlag,
-} from "@remit/api-http-client/types.gen.ts";
-import { useMutation, useQueryClient } from "@tanstack/react-query";
-import { useErrorBanners } from "@/components/ui/ErrorBannerProvider";
-import { buildMutationErrorBanner } from "@/components/ui/error-banners";
-import type { SnapshotEntry } from "@/lib/thread-list-cache";
-
-interface UseToggleTrustedOptions {
-	messageId: string;
-}
-
-interface ToggleTrustedContext {
-	describePrefix: readonly unknown[];
-	previous: SnapshotEntry<RemitImapDescribeMessageResponse>[];
-}
-
-export const buildTrustedFlag = (
-	nextTrusted: boolean,
-	now: number = Date.now(),
-): RemitImapTrustedFlag => ({
-	value: nextTrusted,
-	setAt: now,
-});
-
-export const patchEnvelopeAddress = (
-	addr: RemitImapEnvelopeAddressResponse,
-	addressId: string,
-	nextTrusted: boolean,
-	now?: number,
-): RemitImapEnvelopeAddressResponse => {
-	if (addr.addressId !== addressId) return addr;
-	const flags: RemitImapAddressFlags = { ...(addr.flags ?? {}) };
-	if (nextTrusted) {
-		flags.trusted = buildTrustedFlag(true, now);
-	} else {
-		delete flags.trusted;
-	}
-	return { ...addr, flags };
-};
-
-export const patchDescribeMessage = (
-	data: RemitImapDescribeMessageResponse,
-	addressId: string,
-	nextTrusted: boolean,
-	now?: number,
-): RemitImapDescribeMessageResponse => {
-	const map = (list: RemitImapEnvelopeAddressResponse[]) =>
-		list.map((addr) => patchEnvelopeAddress(addr, addressId, nextTrusted, now));
-	return {
-		...data,
-		envelope: {
-			...data.envelope,
-			from: map(data.envelope.from),
-			to: map(data.envelope.to),
-			cc: map(data.envelope.cc),
-			bcc: map(data.envelope.bcc),
-			replyTo: map(data.envelope.replyTo),
-		},
-	};
-};
-
-/**
- * Toggle the per-sender `trusted` flag for an Address. Mirrors the optimistic-
- * update + rollback pattern from `useToggleStar`: we patch every cached
- * `describeMessage` response that mentions this address so the UI flips
- * instantly, then roll back on error per the project's "never hide failure"
- * rule. The failure is surfaced reliably here in `onError` (banner + rollback),
- * not via a fragile consumer effect; a fatal 5xx additionally escalates through
- * the global MutationCache.onError sink.
- */
-export const useToggleTrusted = ({ messageId }: UseToggleTrustedOptions) => {
-	const queryClient = useQueryClient();
-	const { pushError } = useErrorBanners();
-
-	const { mutate, isPending, error, reset } = useMutation({
-		...addressDetailOperationsUpdateAddressMutation(),
-		onMutate: async (vars): Promise<ToggleTrustedContext> => {
-			const addressId = vars.path.addressId;
-			const trustedPatch = vars.body.flags?.trusted;
-			const nextTrusted = trustedPatch?.value === true;
-
-			const describePrefix = messageOperationsDescribeMessageQueryKey({
-				path: { messageId },
-			});
-
-			await queryClient.cancelQueries({ queryKey: describePrefix });
-
-			const previous = queryClient
-				.getQueriesData<RemitImapDescribeMessageResponse>({
-					queryKey: describePrefix,
-				})
-				.filter(
-					(
-						entry,
-					): entry is [readonly unknown[], RemitImapDescribeMessageResponse] =>
-						entry[1] !== undefined,
-				)
-				.map(([queryKey, data]) => ({ queryKey, data }));
-
-			queryClient.setQueriesData<RemitImapDescribeMessageResponse>(
-				{ queryKey: describePrefix },
-				(old) =>
-					old ? patchDescribeMessage(old, addressId, nextTrusted) : old,
-			);
-
-			return { describePrefix, previous };
-		},
-		onError: (err, _vars, context) => {
-			if (context) {
-				for (const entry of context.previous) {
-					queryClient.setQueryData(entry.queryKey, entry.data);
-				}
-			}
-			pushError(
-				buildMutationErrorBanner(
-					"Couldn't trust sender",
-					"The change wasn't saved.",
-					err,
-				),
-			);
-		},
-		onSettled: (_data, _err, _vars, context) => {
-			if (!context) return;
-			queryClient.invalidateQueries({ queryKey: context.describePrefix });
-		},
-	});
-
-	const toggleTrusted = (addressId: string, currentlyTrusted: boolean) => {
-		const next = !currentlyTrusted;
-		// Always send a TrustedFlag object (value: true|false). The schema
-		// nominally accepts `trusted: null` to remove the flag, but our
-		// openapi-backend validator doesn't honour `nullable: true` on a
-		// schema wrapped in `allOf: [$ref]` (which is how TypeSpec emits
-		// `TrustedFlag | null` for OAS 3.0), so the server rejected untrust
-		// requests as invalid. `{ value: false }` reads as "not trusted"
-		// everywhere (every check is `flags?.trusted?.value === true`) and
-		// also leaves an audit timestamp on the flag.
-		mutate({
-			path: { addressId },
-			body: {
-				flags: {
-					trusted: buildTrustedFlag(next),
-				},
-			},
-		});
-	};
-
-	return { toggleTrusted, isPending, error, reset };
-};

package/src/hooks/useTriageLayer.ts

@@ -1,167 +0,0 @@
-/**
- * The pane-level interaction layer: the bridge between a mounted list and the
- * global keyboard dispatcher, plus next/previous adjacency.
- *
- * The list publishes `MessageListCommands` into `listCommandsRef` and reports
- * its cursor and selection through `onTriageContextChange`; the keyboard hook
- * registers the navigation and selection keys only while a list is serving
- * them, so with no list mounted Enter, Space and ⌘A stay with the browser.
- *
- * This lived inside `MailboxPane`, which is why the brief and Flagged had a
- * keyboard hint bar and no keyboard (#149). Every pane mounts it now.
- *
- * It is two hooks because a pane's verbs are aimed at the focused row: the
- * context comes first, the pane builds its handlers from it, and the keyboard
- * registration comes last.
- *
- * A modal open over the pane is not this layer's problem. Every overlay declares
- * itself on the shared stack (`@remit/ui`'s `overlay-scope`) and `useTriageKeyboard`
- * contains what the top frame does not serve, so the pane no longer reports which
- * of its own dialogs is up and every other layer on the page suspends with it.
- *
- * While a thread is open, `ConversationView` binds its own window listener for
- * the messages inside it, and both used to act on one press (#723). The split
- * is the one `shortcut-tree` already declares: the cursor keys belong to
- * whichever surface has a list on screen, and answering a thread belongs to
- * the open thread — so `hasOpenThread` hands r, a and f over, and the list
- * keeps j/k, Home/End and Enter for as long as it is mounted.
- */
-import { type TriageHandlers, useTriageKeyboard } from "@remit/ui";
-import { type RefObject, useCallback, useRef, useState } from "react";
-import type { MessageListCommands } from "@/components/mail/MessageList";
-import { adjacentMessageId } from "@/lib/adjacent-message";
-
-export interface TriageContextUpdate {
-	focusedMessageId: string | undefined;
-	selectedIds: string[];
-	hasList: boolean;
-	/** Row ids in display order, when the list knows them. Feeds adjacency. */
-	orderedIds?: string[];
-}
-
-export interface TriageContext {
-	listCommandsRef: RefObject<MessageListCommands | null>;
-	onTriageContextChange: (context: TriageContextUpdate) => void;
-	/** The list's roving cursor — where a verb with no selection is aimed. */
-	focusedMessageId: string | undefined;
-	/** The list's checkbox set — what a verb targets when it is non-empty. */
-	selectedIds: string[];
-	/** Row ids in display order, as last reported by the list. */
-	orderedIds: string[];
-	hasList: boolean;
-}
-
-export const useTriageContext = (): TriageContext => {
-	const [focusedMessageId, setFocusedMessageId] = useState<string | undefined>(
-		undefined,
-	);
-	const [selectedIds, setSelectedIds] = useState<string[]>([]);
-	const [orderedIds, setOrderedIds] = useState<string[]>([]);
-	// Null whenever no list is mounted (reading-only phone view, drafts) — the
-	// keyboard layer then simply has nothing to drive.
-	const listCommandsRef = useRef<MessageListCommands | null>(null);
-	const [hasList, setHasList] = useState(false);
-
-	const onTriageContextChange = useCallback((context: TriageContextUpdate) => {
-		setFocusedMessageId(context.focusedMessageId);
-		setSelectedIds(context.selectedIds);
-		if (context.orderedIds) setOrderedIds(context.orderedIds);
-		setHasList(context.hasList);
-	}, []);
-
-	return {
-		listCommandsRef,
-		onTriageContextChange,
-		focusedMessageId,
-		selectedIds,
-		orderedIds,
-		hasList,
-	};
-};
-
-interface UseTriageLayerOptions {
-	context: TriageContext;
-	/** Message ids in display order — the adjacency source for next/previous. */
-	orderedIds: string[];
-	selectedMessageId: string | undefined;
-	/** Suspend the whole layer (e.g. a compose surface owns the keyboard). */
-	enabled?: boolean;
-	/** Close the open thread. Runs only when there is no selection to unwind. */
-	onClose: () => void;
-	/** The pane's own verbs — reply, star, delete and the rest. */
-	handlers: TriageHandlers;
-	/**
-	 * A thread is open, so `ConversationView` is mounted and answers for it.
-	 * This layer drops the three verbs aimed at a whole message — `reply`,
-	 * `replyAll` and `forward` — while that is true, so one press opens one
-	 * reply (#723) and `a` can never answer a different message than `r` just
-	 * did. The cursor keys are not in here: a mounted list keeps those at every
-	 * width, and it is the conversation that stands down from them wherever the
-	 * list is on screen beside it (`ConversationView.listOnScreen`).
-	 */
-	hasOpenThread?: boolean;
-}
-
-export interface TriageLayer {
-	/** Esc: unwinds the selection first, then the open thread. */
-	goBack: () => void;
-	nextMessageId: string | undefined;
-	previousMessageId: string | undefined;
-}
-
-export const useTriageLayer = ({
-	context,
-	orderedIds,
-	selectedMessageId,
-	enabled = true,
-	onClose,
-	handlers,
-	hasOpenThread = false,
-}: UseTriageLayerOptions): TriageLayer => {
-	const { listCommandsRef, hasList } = context;
-
-	const goBack = useCallback(() => {
-		if (listCommandsRef.current?.clearSelection()) return;
-		if (selectedMessageId) onClose();
-	}, [listCommandsRef, selectedMessageId, onClose]);
-
-	// Dropped rather than kept and guarded: an unregistered action is never
-	// preventDefault-ed (see useTriageKeyboard), so the keystroke falls through
-	// to ConversationView's own listener instead of two handlers racing on one
-	// keypress.
-	const { reply, replyAll, forward, ...restHandlers } = handlers;
-
-	useTriageKeyboard({
-		enabled,
-		handlers: {
-			// Registered only while a list is mounted to serve them. An unregistered
-			// action is never preventDefault-ed, so with no list the browser keeps
-			// Enter, Space and ⌘A — select-all-text in the reading pane still works.
-			...(hasList
-				? {
-						focusNext: () => listCommandsRef.current?.focusNext(),
-						focusPrevious: () => listCommandsRef.current?.focusPrevious(),
-						focusFirst: () => listCommandsRef.current?.focusFirst(),
-						focusLast: () => listCommandsRef.current?.focusLast(),
-						openFocused: () => listCommandsRef.current?.openFocused(),
-						toggleSelect: () => listCommandsRef.current?.toggleSelect(),
-						extendSelectDown: () => listCommandsRef.current?.extendSelectDown(),
-						extendSelectUp: () => listCommandsRef.current?.extendSelectUp(),
-						selectAll: () => listCommandsRef.current?.selectAll(),
-						toggleDensity: () => listCommandsRef.current?.toggleDensity(),
-					}
-				: {}),
-			back: goBack,
-			...restHandlers,
-			...(hasOpenThread ? {} : { reply, replyAll, forward }),
-		},
-	});
-
-	return {
-		goBack,
-		nextMessageId:
-			adjacentMessageId(orderedIds, selectedMessageId, "next") ?? undefined,
-		previousMessageId:
-			adjacentMessageId(orderedIds, selectedMessageId, "previous") ?? undefined,
-	};
-};

package/src/hooks/useTriggerSync.test.ts

@@ -1,18 +0,0 @@
-import assert from "node:assert/strict";
-import { describe, test } from "node:test";
-import { mailboxOperationsListMailboxesQueryKey } from "@remit/api-http-client/@tanstack/react-query.gen.ts";
-import { buildMailboxListKey } from "./useTriggerSync.js";
-
-describe("buildMailboxListKey", () => {
-	test("matches the generated SDK query key for the same accountId", () => {
-		// On success the trigger-sync mutation invalidates this key — if it
-		// drifts from the generated SDK key, the freshly-synced mailbox rows
-		// will not be re-fetched. Pin the contract.
-		const accountId = "acc-1234";
-		const got = buildMailboxListKey(accountId);
-		const want = mailboxOperationsListMailboxesQueryKey({
-			path: { accountId },
-		});
-		assert.deepEqual(got, want);
-	});
-});

package/src/hooks/useTriggerSync.ts

@@ -1,64 +0,0 @@
-import {
-	mailboxOperationsListMailboxesQueryKey,
-	syncOperationsTriggerSyncMutation,
-} from "@remit/api-http-client/@tanstack/react-query.gen.ts";
-import { useMutation, useQueryClient } from "@tanstack/react-query";
-import { useTelemetry } from "@/lib/telemetry-context";
-
-interface UseTriggerSyncResult {
-	trigger: () => void;
-	triggerAsync: () => Promise<unknown>;
-	isPending: boolean;
-	// TanStack types this as the generated wire body now that the operation
-	// declares its failures; by the time it arrives, `client.ts`'s error
-	// interceptor has re-wrapped it as an `ApiError` and `taggedFetch` a
-	// transport failure as a `NetworkError`. `unknown` is what the declared type
-	// and the real one agree on, and every reader goes through
-	// `formatErrorMessage`.
-	error: unknown;
-	reset: () => void;
-}
-
-/**
- * Build the TanStack query key for the mailbox-list query owned by the
- * given account. Extracted from the hook so the staleness/invalidation
- * contract can be unit-tested without rendering React.
- */
-export const buildMailboxListKey = (accountId: string) =>
-	mailboxOperationsListMailboxesQueryKey({ path: { accountId } });
-
-/**
- * Trigger a server-side mailbox-list sync for an account.
- *
- * Wraps the generated `syncOperationsTriggerSync` mutation. The backend
- * enqueues a SYNC_MAILBOXES SQS event and the worker picks it up; the
- * mutation resolves as soon as the enqueue ack returns, not when the
- * sync itself finishes. We invalidate the account's mailboxes query on
- * success so the freshly-synced rows are re-fetched once the worker
- * writes them — TanStack will pick the new data up via its background
- * refetch on the next render.
- */
-export const useTriggerSync = (accountId: string): UseTriggerSyncResult => {
-	const queryClient = useQueryClient();
-	const telemetry = useTelemetry();
-
-	const mutation = useMutation({
-		...syncOperationsTriggerSyncMutation(),
-		onSuccess: () => {
-			telemetry.recordEvent("sync.triggered");
-			queryClient.invalidateQueries({
-				queryKey: buildMailboxListKey(accountId),
-			});
-		},
-	});
-
-	return {
-		trigger: () => {
-			mutation.mutate({ path: { accountId } });
-		},
-		triggerAsync: () => mutation.mutateAsync({ path: { accountId } }),
-		isPending: mutation.isPending,
-		error: mutation.error,
-		reset: mutation.reset,
-	};
-};