Maximilian Stubhan
b87c8ad64c
The database moved to a container of our own; the platform is gone. This takes out what was left of it — and, where the leftovers were load bearing, moves rather than deletes. Moved, not deleted: supabase/migrations/ -> db/migrations/ the schema's source of truth supabase/build-org.ts -> scripts/build-org.ts lib/supabase/types.ts -> lib/types.ts 52 import sites repointed The bookkeeping needed care. It lived in `supabase_migrations.schema_migrations`, and simply renaming the schema would have left the runner facing an empty table: it would have called all 67 migrations pending and replayed them against a database that is long since current. So the runner now creates `migrationen.schema_migrations` and, once, copies the old rows across — guarded so a second run does nothing and a fresh database skips it entirely. Only then does migration 20260907100000 drop the old schema. Deleted: the CLI config, the seed, the historical schema/function dumps (nothing read them), scripts/umzug-von-supabase.sh (the move is done), and both Supabase packages plus the CLI. Nothing in the application imported them — the build now succeeds with no environment variables at all, which is the proof. Integration tests: six of them signed in through Supabase Auth and asserted against the anon key and the service role. That model is gone, so the tests were not portable — they are deleted. session-context and employee-status-filter already ran on pg and are untouched; om-reporting is ported to a direct connection because it guards a real risk (the reporting line rule exists twice, once in SQL and once in TypeScript). CI: the integration job started a Supabase stack. It now runs a postgres service, applies deploy/db-init and every migration to an empty database — that was the valuable part, and it still holds — then checks that a second run is a no-op, which is what proves the bookkeeping works. Docs: security-review.md audited a service-role key, a cookie adapter and auth.users, none of which exist. Restating findings about removed components would suggest today's system had been reviewed; it has not. It now records what was removed and says a fresh review is due. data-model.md was already marked obsolete and described the pre-OM schema; azure-migration.md was a plan for a route not taken. Both deleted. Verified: npm ci, typecheck, lint, 445 tests, build — all clean without the packages. Integration tests skip cleanly with no database. Migration SQL and the runner are reviewed but NOT executed: no Docker here, and the old instance no longer resolves. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
86 lines
3.0 KiB
TypeScript
86 lines
3.0 KiB
TypeScript
"use client";
|
||
|
||
import { useRouter } from "next/navigation";
|
||
import { useState } from "react";
|
||
import { promoteEmployee } from "@/actions/employees";
|
||
import { Button } from "@/components/ui/Button";
|
||
import { SelectField, TextField } from "@/components/ui/Field";
|
||
import { SlideOver } from "@/components/ui/SlideOver";
|
||
import { useToast } from "@/components/ui/Toast";
|
||
import type { Database, PaygradeType } from "@/lib/types";
|
||
import { fmtName } from "@/lib/format";
|
||
|
||
type EmployeeRow = Database["public"]["Tables"]["employees"]["Row"];
|
||
|
||
const PAYGRADES: { value: PaygradeType; label: string }[] = [
|
||
{ value: "A", label: "A – Einstieg" },
|
||
{ value: "B", label: "B – Qualifiziert" },
|
||
{ value: "C", label: "C – Erfahren" },
|
||
{ value: "D", label: "D – Spezialist:in" },
|
||
{ value: "E", label: "E – Teamleitung" },
|
||
{ value: "F", label: "F – Bereichsleitung / GF" },
|
||
];
|
||
|
||
export function PromotePanel({ open, onClose, employee }: { open: boolean; onClose: () => void; employee: EmployeeRow }) {
|
||
const { showToast } = useToast();
|
||
const router = useRouter();
|
||
const [effectiveDate, setEffectiveDate] = useState("");
|
||
const [newTitle, setNewTitle] = useState(employee.job_title);
|
||
const [paygrade, setPaygrade] = useState<PaygradeType>(employee.paygrade);
|
||
const [pending, setPending] = useState(false);
|
||
|
||
async function handleSubmit() {
|
||
if (!effectiveDate || !newTitle) {
|
||
showToast("Bitte alle Pflichtfelder ausfüllen.", "error");
|
||
return;
|
||
}
|
||
setPending(true);
|
||
const result = await promoteEmployee({
|
||
employee_id: employee.id,
|
||
effective_date: effectiveDate,
|
||
new_title: newTitle,
|
||
new_paygrade: paygrade,
|
||
});
|
||
setPending(false);
|
||
if (result.success) {
|
||
showToast(`${employee.first_name} ${employee.last_name} wurde befördert.`);
|
||
router.refresh();
|
||
onClose();
|
||
} else {
|
||
showToast(result.error ?? "Fehler beim Speichern.", "error");
|
||
}
|
||
}
|
||
|
||
return (
|
||
<SlideOver
|
||
open={open}
|
||
onClose={onClose}
|
||
title="Beförderung"
|
||
subtitle={`${fmtName(employee.first_name, employee.last_name)} · ${employee.job_title}`}
|
||
footer={
|
||
<>
|
||
<Button variant="ghost" onClick={onClose}>
|
||
Abbrechen
|
||
</Button>
|
||
{/* Promotion keeps its own purple, matching the Beförderung badge
|
||
used in the history tab. */}
|
||
<Button onClick={handleSubmit} pending={pending} className="!bg-purple-text text-white hover:brightness-110">
|
||
Befördern
|
||
</Button>
|
||
</>
|
||
}
|
||
>
|
||
<div className="flex flex-col gap-4">
|
||
<TextField label="Wirksam ab" required type="date" value={effectiveDate} onChange={setEffectiveDate} />
|
||
<TextField label="Neue Position" required value={newTitle} onChange={setNewTitle} />
|
||
<SelectField
|
||
label="Paygrade"
|
||
value={paygrade}
|
||
onChange={(v) => setPaygrade(v as PaygradeType)}
|
||
options={PAYGRADES}
|
||
/>
|
||
</div>
|
||
</SlideOver>
|
||
);
|
||
}
|