代码提交

frontend-web/src/core/threads/hooks.ts

@@ -1363,8 +1363,8 @@ export function useDeleteThread() {
  * `MessageList`) so the removal shows immediately; a reload then reads the
  * persisted, already-trimmed state.
  */
-export function useDeleteMessage() {
-  return useMutation({
+export function useDeleteMessage() {
+  return useMutation({
     mutationFn: async ({
       threadId,
       messageId,
@@ -1394,12 +1394,92 @@ export function useDeleteMessage() {
       // Fall back to the requested id so the caller can always hide something.
       return body.deleted_ids?.length ? body.deleted_ids : [messageId];
     },
-  });
-}
-
-/**
- * Merge metadata into a conversation's record via the Gateway
- * `PATCH /api/threads/{id}` route. Used to persist per-conversation flags such
+  });
+}
+
+/**
+ * Clear all messages from a thread checkpoint. The caller should immediately
+ * hide the returned ids locally because the active stream cache may still hold
+ * the old message objects until a reload/refetch reads the trimmed checkpoint.
+ */
+export function useClearThreadMessages() {
+  return useMutation({
+    mutationFn: async ({
+      threadId,
+    }: {
+      threadId: string;
+    }): Promise<string[]> => {
+      const response = await apiFetch(
+        `${getBackendBaseURL()}/api/threads/${encodeURIComponent(
+          threadId,
+        )}/messages`,
+        {
+          method: "DELETE",
+        },
+      );
+
+      if (!response.ok) {
+        const error = await response
+          .json()
+          .catch(() => ({ detail: "清空对话失败。" }));
+        throw new Error(error.detail ?? "清空对话失败。");
+      }
+
+      const body = (await response.json().catch(() => ({}))) as {
+        deleted_ids?: string[];
+      };
+      return body.deleted_ids ?? [];
+    },
+  });
+}
+
+/**
+ * Persist an in-place message edit in the latest thread checkpoint.
+ *
+ * This is opt-in UI behaviour: most chat pages keep their existing
+ * "edit question and resubmit" affordance, while position roundtable can pass
+ * this mutation down to save the original message content itself.
+ */
+export function useEditMessage() {
+  return useMutation({
+    mutationFn: async ({
+      threadId,
+      messageId,
+      content,
+    }: {
+      threadId: string;
+      messageId: string;
+      content: string;
+    }): Promise<Message> => {
+      const response = await apiFetch(
+        `${getBackendBaseURL()}/api/threads/${encodeURIComponent(
+          threadId,
+        )}/messages/${encodeURIComponent(messageId)}`,
+        {
+          method: "PATCH",
+          headers: { "Content-Type": "application/json" },
+          body: JSON.stringify({ content }),
+        },
+      );
+
+      if (!response.ok) {
+        const error = await response
+          .json()
+          .catch(() => ({ detail: "消息保存失败。" }));
+        throw new Error(error.detail ?? "消息保存失败。");
+      }
+
+      const body = (await response.json().catch(() => ({}))) as {
+        message?: Message;
+      };
+      return body.message ?? ({ id: messageId, type: "human", content } as Message);
+    },
+  });
+}
+
+/**
+ * Merge metadata into a conversation's record via the Gateway
+ * `PATCH /api/threads/{id}` route. Used to persist per-conversation flags such
  * as `is_pinned` (置顶) and `is_favorite` (收藏) — a conversation belongs to a
  * single user, so these live directly on the thread metadata (no join table).
  * Updates the `["threads", "search"]` cache optimistically so the UI reflects