g1t/apps/web/app/routes/settings/security-log.tsx

18 lines699 bytesCodeBlame

Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.

status.g1t.sh with incident management, invites that land you in the workspace, settings as pages, usage without quotas1import type { Route } from "./+types/security-log";
2import { page } from "../../lib/meta";
3import { requireUser } from "../../lib/session.server";
4import { SecurityLogSection } from "../../components/emails-section";
5import { loadSecurityLog } from "../../lib/emails.server";
6
7export function meta(args: Route.MetaArgs) {
8 return page(args, { title: "Security log · Settings · g1t" });
9}
10
11export async function loader({ request, context }: Route.LoaderArgs) {
12 const user = requireUser(context, request);
13 return { log: await loadSecurityLog(user) };
14}
15
16export default function SecurityLogSettings({ loaderData }: Route.ComponentProps) {
17 return <SecurityLogSection log={loaderData.log} />;
18}