feat(web): complete groups/contacts/favorites/settings/calls/system domains + extensive review-round fixes

Rounds out the full rewrite with the remaining feature domains: group management (admin panel, mute, files, announcements, QR-based invite/join), contacts (friend profile, add-friend, blocklist, new-friends), favorites (real media rendering across text/image/video/voice/file/link), settings (profile/security/privacy/general/about), calls (Agora-backed audio/video signaling + call history), and system messages/file assistant. Also folds in a large batch of live-verified fixes surfaced by repeated fresh code-review passes and hands-on E2E testing against the real backend, including: WS reconnect not resubscribing any topic after a disconnect, missing x-im-client-mid on every send path (protocol compliance for retry dedup), group mute/member-settings/self-profile endpoint corrections, relationship-state type fixes across search/QR/ friend-profile, tenant-switch logout gap, password-policy now read from the real per-tenant config instead of guessed, NavRail highlight/ aria-current desync, several call-state-machine races, and responsive layout fixes across all four breakpoints (mobile/tablet/laptop/desktop) including a full mobile rebuild of favorites, call UI, and the settings home/sub-list split. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-09 20:16:33 +08:00
parent 72b7b79caf
commit 5c3f3b7653
89 changed files with 10158 additions and 442 deletions
@@ -0,0 +1,44 @@
+import { useState } from 'react';
+
+import { Toast } from '@/app/Toast';
+
+/**
+ * README §8.7 mentions a "清空缓存「126 MB」" row -- confirmed no server endpoint touches cache at
+ * all (docs/IM-后端问题清单.md-adjacent research: "No backend endpoint clears cache/history -- both
+ * are pure client-side operations"). Computing a real, honest "just this app's cache" byte count is
+ * not reliably possible (`navigator.storage.estimate()` reports the WHOLE origin, not a
+ * per-feature breakdown) -- rather than show a fabricated-looking number, this omits the size and
+ * just performs and confirms the real clear (this app's own Cache Storage buckets, per the SW-
+ * caching behavior already relied on elsewhere in this app).
+ */
+export function GeneralSettingsPage() {
+  const [status, setStatus] = useState<'idle' | 'clearing' | 'done'>('idle');
+  const [error, setError] = useState('');
+
+  const clearCache = async () => {
+    if (!window.confirm('确定清除本地缓存吗？不会影响你的账号数据。')) return;
+    setStatus('clearing');
+    try {
+      if (typeof caches === 'undefined') throw new Error('此浏览器不支持缓存清除');
+      const keys = await caches.keys();
+      await Promise.all(keys.map((k) => caches.delete(k)));
+      setStatus('done');
+    } catch (err) {
+      setStatus('idle');
+      setError(err instanceof Error ? err.message : '清除缓存失败，请重试');
+    }
+  };
+
+  return (
+    <div className="mx-auto w-full max-w-[720px] px-5 py-8 md:px-10">
+      <h2 className="mb-4 text-xl font-semibold text-text-heading">通用</h2>
+      <div className="rounded-xl bg-white text-sm">
+        <button type="button" onClick={clearCache} disabled={status === 'clearing'} className="flex w-full items-center justify-between px-7 py-4 text-left">
+          <span className="text-text-body">清空缓存</span>
+          <span className="text-text-tertiary-2">{status === 'clearing' ? '清除中…' : status === 'done' ? '已清除 ›' : '›'}</span>
+        </button>
+      </div>
+      <Toast message={error} variant="error" onDone={() => setError('')} />
+    </div>
+  );
+}