@remit/web-client 0.0.326 → 0.0.327

package/dist/src/components/mail/MailboxPane.js

@@ -23,7 +23,7 @@ import { useInfiniteQuery } from "@tanstack/react-query";
 import { createContext, useCallback, useContext, useEffect, useMemo, useRef, useState, } from "react";
 import { useArchiveMailbox, useDraftsMailbox, useJunkMailbox, useTrashByAccount, useTrashMailbox, } from "../../hooks/useArchiveMailbox";
 import { useCurrentMailboxMessageCount, useCurrentMailboxName, useCurrentMailboxUnseenCount, } from "../../hooks/useCurrentMailboxName";
-import { dropDeletedThreads, useDeleteMessages, } from "../../hooks/useDeleteMessages";
+import { useDeleteMessages } from "../../hooks/useDeleteMessages";
 import { useEmptyTrash } from "../../hooks/useEmptyTrash";
 import { useIntelligenceData } from "../../hooks/useIntelligenceData";
 import { useIntelligenceDrawer } from "../../hooks/useIntelligenceDrawer";
@@ -191,14 +191,7 @@ function MailboxPaneProvider({ mailboxId, thread, children, }) {
     });
     const { accountId: mailboxAccountId, isLoading: mailboxAccountLoading } = useMailboxAccount(mailboxId);
     const mailboxName = useCurrentMailboxName({ accounts });
-    // The server answered the active predicate, so these rows are the list: the
-    // dedupe spans pages and the deleted drop repeats the server's own
-    // `excludeDeleted`, and neither result changes when another page loads.
-    // Residual tokens are the exception — the request could not carry them, so
-    // they are applied here over what came back. That thins a page rather than
-    // answering over the whole mailbox, which is why the empty state stops
-    // claiming the folder was read and the escalation predicate is withheld.
-    const threads = applyResidualTokens(dropDeletedThreads(dedupeThreadMessages(threadsData?.pages.flatMap((page) => page.items ?? []) ?? [])), residualTokens, mailboxAccountId);
+    const threads = applyResidualTokens(dedupeThreadMessages(threadsData?.pages.flatMap((page) => page.items ?? []) ?? []), residualTokens, mailboxAccountId);
     const onSelectFilterCategory = useCallback((id) => {
         setFilterCategory(id);
     }, []);

package/dist/src/hooks/useDeleteFolder.js

@@ -30,8 +30,6 @@ const collectMovableIds = async (mailboxId, alreadyMoved, limit, signal) => {
             throwOnError: true,
         });
         for (const item of data.items) {
-            if (item.isDeleted)
-                continue;
             if (alreadyMoved.has(item.messageId))
                 continue;
             if (ids.includes(item.messageId))
@@ -63,11 +61,7 @@ const liveMessageCount = async (mailboxId, signal) => {
             query: { order: "desc", continuationToken },
             throwOnError: true,
         });
-        for (const item of data.items) {
-            if (item.isDeleted)
-                continue;
-            count += 1;
-        }
+        count += data.items.length;
         if (!data.continuationToken)
             break;
         continuationToken = data.continuationToken;

package/dist/src/hooks/useDeleteMessages.d.ts

@@ -25,15 +25,6 @@ interface UseDeleteMessagesOptions {
  * the set are removed.
  */
 export declare const removeMessagesFromItems: (items: RemitImapThreadMessageResponse[], messageIds: Set<string>) => RemitImapThreadMessageResponse[];
-/**
- * Pure helper: drop soft-deleted rows from a flattened thread list.
- *
- * Belt-and-braces guard against #212. The backend already excludes
- * `isDeleted: true` rows from the inbox listing, but if a regression slips
- * back in (or an eventual-consistency window briefly returns a soft-deleted
- * row) the UI must not show it.
- */
-export declare const dropDeletedThreads: (items: RemitImapThreadMessageResponse[]) => RemitImapThreadMessageResponse[];
 export declare const useDeleteMessages: ({ mailboxId, threadId, accountId, messages, onAfterOptimisticRemove, }: UseDeleteMessagesOptions) => {
     deleteMessages: (messageIds: string[]) => void;
     isPending: boolean;

package/dist/src/hooks/useDeleteMessages.js

@@ -18,15 +18,6 @@ import { resolveMailboxesForMessages } from "./useMarkAsRead";
  * the set are removed.
  */
 export const removeMessagesFromItems = (items, messageIds) => items.filter((item) => !messageIds.has(item.messageId));
-/**
- * Pure helper: drop soft-deleted rows from a flattened thread list.
- *
- * Belt-and-braces guard against #212. The backend already excludes
- * `isDeleted: true` rows from the inbox listing, but if a regression slips
- * back in (or an eventual-consistency window briefly returns a soft-deleted
- * row) the UI must not show it.
- */
-export const dropDeletedThreads = (items) => items.filter((item) => item.isDeleted !== true);
 export const useDeleteMessages = ({ mailboxId, threadId, accountId, messages, onAfterOptimisticRemove, }) => {
     const queryClient = useQueryClient();
     const { pushError } = useErrorBanners();

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@remit/web-client",
-	"version": "0.0.326",
+	"version": "0.0.327",
 	"type": "module",
 	"description": "Remit web client, published as composable primitives — the app shell, auth shells, and runtime config. A distributor imports what it composes and bundles it.",
 	"exports": {