同步bug

[NightYuYyy]

点击删除后，前端页面没有实时刷新 然后点编辑用户里面已删除的key 还存在 保存会提示key不存在 （实际这个key 已经删除了）

[github-actions]

Thank you for reporting this UI synchronization issue.

Analysis:

I've investigated the codebase and identified what's happening:

1. Key deletion flow: When a key is deleted via the delete button (src/app/[locale]/dashboard/_components/user/forms/delete-key-confirm.tsx), the server action removeKey in src/actions/keys.ts (lines 461-525) is called, which:

   • Performs the database deletion successfully
   • Calls revalidatePath("/dashboard") at line 519

2. The sync issue: The problem you're experiencing occurs in the unified edit dialog (src/app/[locale]/dashboard/_components/user/unified-edit-dialog.tsx). When editing a user:

   • The dialog loads the user's keys into local form state at initialization (lines 272-275)
   • If a key is deleted elsewhere (e.g., from the key list view), the dialog's local state is not automatically updated
   • The router.refresh() in delete-key-confirm.tsx (line 42) triggers a page refresh, but if the unified edit dialog is already open with stale data, it won't reflect the deletion

3. Root cause: The unified edit dialog maintains its own local state for keys (form.values.keys). When a key is deleted through the separate KeyActions component, the dialog doesn't receive this update because:

   • The dialog caches the user's keys on mount
   • The deletedKeyIds state (line 233) only tracks keys deleted within the dialog itself
   • There's no mechanism to sync external key deletions into an already-open dialog

Potentially affected code:

• src/app/[locale]/dashboard/_components/user/unified-edit-dialog.tsx (lines 272-275, 476-482) - local key state management
• src/app/[locale]/dashboard/_components/user/forms/delete-key-confirm.tsx (lines 32-47) - external delete handler
• src/app/[locale]/dashboard/_components/user/key-actions.tsx - delete action trigger

Workaround:
For now, after deleting a key, close the edit dialog and reopen it to see the updated key list.

---

Automated response from Claude AI

[github-actions]

谢谢反馈。

分析（基于当前代码）

• 后端删除 Key 走 removeKey：先 findKeyById，不存在则返回“密钥不存在”，随后调用 deleteKey 软删并 revalidatePath("/dashboard")（src/actions/keys.ts#L461、src/actions/keys.ts#L469、src/actions/keys.ts#L514、src/actions/keys.ts#L519；src/repository/key.ts#L379）。
• /dashboard/users 的列表数据来自 TanStack Query useInfiniteQuery，并且 QueryClient 设置了 staleTime: 30000、refetchOnWindowFocus: false（src/app/[locale]/dashboard/users/users-page-client.tsx#L26、src/app/[locale]/dashboard/users/users-page-client.tsx#L79、src/app/[locale]/dashboard/users/users-page-client.tsx#L96）。
• 在用户列表里点 Key 的删除按钮时，代码路径是 handleDeleteKey -> removeKey -> router.refresh()，但这条路径没有对 users 查询做显式 invalidateQueries（src/app/[locale]/dashboard/_components/user/user-key-table-row.tsx#L139）。对比：编辑弹窗提交成功后会 queryClient.invalidateQueries({ queryKey: ["users"] })（src/app/[locale]/dashboard/_components/user/unified-edit-dialog.tsx#L489）。
• 编辑弹窗拿到的 user 来自当前内存里的 users 列表：editingUser = users.find(...) 并传给 UnifiedEditDialog（src/app/[locale]/dashboard/_components/user/user-management-table.tsx#L276、src/app/[locale]/dashboard/_components/user/user-management-table.tsx#L565）。如果列表未更新，就会把已删除的 key 仍带进表单；保存时会调用 editKey，而 editKey 在找不到 key 时会返回“密钥不存在”（src/actions/keys.ts#L280、src/actions/keys.ts#L317）。

为了进一步确认

• 你是在 /dashboard/users 里直接点 key 行的删除（Trash 图标）触发的吗？还是在编辑弹窗里删除？（两条路径的刷新/缓存处理不同）

临时 workaround

• 删除后手动刷新页面；重新拉取用户/Key 列表时会过滤 deletedAt 不为空的 key（src/repository/key.ts#L77、src/repository/key.ts#L106）。

---

Automated response from Codex AI