Arnaud
4c3880e07f
Moderator role existed in the schema and was already respected by
comment deletion, but every admin page/route treated moderator
identically to a regular user (403/redirect). Wires it up narrowly:
admin/layout.tsx now lets admin+moderator through and filters the
nav by role, while every admin-only page (users, tiers, settings,
webhooks, insights, etc.) explicitly redirects moderators away via a
new requireFullAdminPage() helper -- the nav filter is UX, this is
the actual gate. Moderators land on Reports and Recipes: reports
GET/PATCH now accept requireAdmin({allowModerator: true}), and a new
PATCH /api/v1/admin/recipes/[id] lets admin+moderator unpublish a
public recipe (flip to private) as a takedown action, audit-logged.
Also found and fixed a real bug while auditing the PWA push pipeline
for a "push click-through" gap: public/sw.js had no `push` event
listener at all, so incoming push messages never displayed anything
-- push was silently non-functional end-to-end despite the
subscribe/send plumbing all working. Added the push listener
(showNotification) and a notificationclick listener that focuses an
existing tab or opens one at the payload's url.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
34 lines
1.2 KiB
TypeScript
34 lines
1.2 KiB
TypeScript
import type { Metadata } from "next";
|
|
import { db, adminWebhooks } from "@epicure/db";
|
|
import { AdminWebhooksManager } from "@/components/admin/admin-webhooks-manager";
|
|
import { requireFullAdminPage } from "@/lib/require-admin-page";
|
|
|
|
export const metadata: Metadata = {};
|
|
|
|
export default async function AdminWebhooksPage() {
|
|
await requireFullAdminPage();
|
|
const rows = await db
|
|
.select({
|
|
id: adminWebhooks.id,
|
|
url: adminWebhooks.url,
|
|
events: adminWebhooks.events,
|
|
active: adminWebhooks.active,
|
|
createdAt: adminWebhooks.createdAt,
|
|
})
|
|
.from(adminWebhooks);
|
|
|
|
const webhooks = rows.map((w) => ({ ...w, createdAt: w.createdAt.toISOString() }));
|
|
|
|
return (
|
|
<div className="space-y-6">
|
|
<div>
|
|
<h1 className="text-2xl font-bold tracking-tight">Webhooks</h1>
|
|
<p className="text-muted-foreground text-sm mt-1">
|
|
Site-wide ops events (new signups, support tickets, reports) — deliver to any HTTP endpoint (Slack/Discord incoming webhook, internal alerting, etc). Fires regardless of who's involved, unlike the per-user webhooks under Settings.
|
|
</p>
|
|
</div>
|
|
<AdminWebhooksManager initialWebhooks={webhooks} />
|
|
</div>
|
|
);
|
|
}
|