Nicolas
0c8cda7f3e
All checks were successful
PR 2/2 de l'issue #80 — la vue admin en lecture seule des messages remontés via le formulaire de contact (PR 1 = #123). - Contrat partagé : `listContactMessagesQuerySchema` (filtre `type` optionnel) + `types/contact.ts` `ContactMessageAdminView` (`author` = `{ id, firstName, lastName, email } | null`, `null` = compte supprimé). - API : `admin-contact.{routes,service}.ts` — `GET /admin/api/contact?type=` (`requireAdmin`), tri `createdAt desc`, plafond `CONTACT_MESSAGES_PAGE_SIZE = 200` (même esprit que `CORRECTIONS_PAGE_SIZE`). Branché dans `admin.routes.ts` (`adminRouter.use(/contact, …)`). Aucune route d'écriture. - Front : page `/admin/messages` (`MessagesPage` + `.scss`) — tableau lecture seule (date, expéditeur ou « Compte supprimé », badge de type, message, page, user-agent tronqué + titre au survol), un filtre par type. Entrée de nav « Messages » (icône `Inbox`) dans `AdminLayout` + `adminApiClient.getContactMessages` + i18n `admin.nav.messages` / `admin.messages.*`. - Tests : `apps/api/test/admin-contact.test.ts` (Mocha — 401 sans session admin, tri récent d'abord + `author` résolu, filtre `type`, type inconnu → 400, plafond 200, `author: null` après suppression du compte), `apps/web/cypress/e2e/admin-messages.cy.ts` (rendu lecture seule, filtre par type via le query param). - Docs : `backend-architecture.md` (section `admin` + event `contact.submitted` dans la liste). Closes #80. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
30 lines
1.4 KiB
TypeScript
30 lines
1.4 KiB
TypeScript
import { Router } from "express";
|
|
import { adminAuthRouter } from "./admin-auth.routes.js";
|
|
import { adminCatalogRouter } from "./admin-catalog.routes.js";
|
|
import { adminContactRouter } from "./admin-contact.routes.js";
|
|
import { adminMetricsRouter } from "./admin-metrics.routes.js";
|
|
import { adminTechStepsRouter } from "./admin-tech-steps.routes.js";
|
|
import { adminToursRouter } from "./admin-tours.routes.js";
|
|
|
|
/**
|
|
* Aggregator for the admin application's API surface, mounted at
|
|
* `/admin/api` in `app.ts` (not bare `/admin` — see that mount point's own
|
|
* comment for why: it would collide with apps/web's `/admin/*` page
|
|
* routes). Every sub-router here backs one of those pages —
|
|
* `/admin/api/auth` is public (login), everything added later
|
|
* (`/admin/api/metrics`, `/admin/api/tech-steps/*`, `/admin/api/catalog/*`)
|
|
* sits behind `requireAdmin` (`middlewares/require-admin.ts`).
|
|
*
|
|
* Monitoring has **no** REST route here on purpose — it's pushed over
|
|
* WebSocket instead (`lib/monitoring-broadcast.service.ts`, wired in
|
|
* `server.ts`), not requested per-page-load. See that service's doc
|
|
* comment for the full mechanism.
|
|
*/
|
|
export const adminRouter = Router();
|
|
|
|
adminRouter.use("/auth", adminAuthRouter);
|
|
adminRouter.use("/metrics", adminMetricsRouter);
|
|
adminRouter.use("/tech-steps", adminTechStepsRouter);
|
|
adminRouter.use("/catalog", adminCatalogRouter);
|
|
adminRouter.use("/tours", adminToursRouter);
|
|
adminRouter.use("/contact", adminContactRouter);
|