asepharyana
8e7ba67248
Build & Deploy (Nix) / build-and-deploy (discord-gateway) (push) Successful in 2m47s
Build & Deploy (Nix) / build-and-deploy (backend) (push) Successful in 3m12s
Build & Deploy (Nix) / build-and-deploy (proxy) (push) Successful in 3m12s
useMessageDetail fetch attachments per-channel -> detail view nampilin 10 image terbaru di channel itu (semua orang), bukan image pesan yang diklik. Root cause: getAttachmentsByChannel cuma filter channel_id. - backend: messageQuerySchema + messageId optional; repository tambah eq(message_id) pas messageId ada. Sudah ada index idx_attachments_message. - frontend: getAttachments(channelId, limit, cursor, messageId); useMessageDetail pass id pesan. Verifikasi: backend tsc PASS, frontend tsc PASS + next build PASS. E2E local (tsx + env prod, port 3901): tanpa messageId -> 3 row (termasuk image.png punya message lain); dengan messageId -> tepat 2 row milik pesan itu. psql juga konfirmasi channel-only 3 vs message-filtered 2.
Bete Frontend
Next.js 16 (React 19) dashboard untuk Discord Moderation Watcher.
Stack: Next.js 16 (App Router, static export), React 19, TypeScript strict, Tailwind v4, shadcn/ui, base-ui, lucide-react.
Dev
bun run dev # next dev — port 3000
bun run build # next build — static export ke out/
bun run lint # Biome check
Architecture
src/
├── app/ # Pages
│ ├── page.tsx # Redirect ke /dashboard
│ └── dashboard/ # Dashboard layout + tabs
│ ├── layout.tsx # Sidebar, header, WS provider, chatbot
│ └── page.tsx # Tab routing (messages/live/dashboard)
├── features/
│ ├── messages/ # Message feed, search, review, detail modal
│ ├── live/ # Voice connection, music player, recordings
│ ├── dashboard/ # Stats, users, channels overview
│ └── chatbot/ # AI chatbot
├── lib/
│ ├── api/ # Fetch-based API client (all BE endpoints)
│ ├── ws/ # WebSocket client + React context
│ └── hooks/ # Shared hooks (config, auth)
└── components/
└── layout/ # Sidebar, header, mobile tab bar
API
Backend berjalan di port 3001. Frontend mengakses API via window.location (same-origin atau proxy).
WebSocket terhubung otomatis ke /ws di host yang sama.