rmancinasandClaude Opus 5
0332292ae9
MailModule's provider used a `useFactory` with no `inject`, so the factory received `undefined` and `new MailService(config)` threw on `config.get`, taking the whole API down at boot. The module also wasn't actually `@Global()` even though both NotificationsModule and RenewalsModule inject MailService without importing it — that would have failed next. Replaced the factory with a plain provider (ConfigModule is already `isGlobal`) and marked the module global. On the web side, mass email and renewal notices were two menu entries doing the same job — telling a customer something by email. They are now two tabs of `/notificaciones` (Servicios and Pólizas), following the Captura pattern: `/renovaciones` still resolves, opening the same screen on its Pólizas tab so existing bookmarks keep working. The notifications page was also the last screen written in raw inline styles, with blue buttons and filter pills that appear nowhere else in the app. It now uses the shared design system: btn-primary/btn-outline, the seg segmented control, card, tx-table, pager, and the servicios/fideicomiso badges. Two supporting fixes found on the way: NOTIFICATION_STATUS_COLORS hardcoded hex instead of the theme's positive/negative/muted vars, and `.small` was referenced in 19 places across the app but never defined in globals.css. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
15 lines
424 B
TypeScript
15 lines
424 B
TypeScript
"use client";
|
|
|
|
import { AppShell } from "@/components/AppShell";
|
|
import { Notificaciones } from "@/components/Notificaciones";
|
|
|
|
/** Renewal notices moved into /notificaciones as its "Pólizas" tab. This route
|
|
* stays so old bookmarks and links land on that tab instead of a 404. */
|
|
export default function RenovacionesPage() {
|
|
return (
|
|
<AppShell>
|
|
<Notificaciones initialTab="polizas" />
|
|
</AppShell>
|
|
);
|
|
}
|