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>
72 lines
3.1 KiB
TypeScript
72 lines
3.1 KiB
TypeScript
import { dienstwagenLabel } from "@/lib/dienstwagen";
|
||
import { fmtDate } from "@/lib/format";
|
||
import type { Database } from "@/lib/types";
|
||
|
||
type EmployeeRow = Database["public"]["Tables"]["employees"]["Row"];
|
||
|
||
const PAYGRADE_LABELS: Record<string, string> = {
|
||
A: "A – Einstieg",
|
||
B: "B – Qualifiziert",
|
||
C: "C – Erfahren",
|
||
D: "D – Spezialist:in",
|
||
E: "E – Teamleitung",
|
||
F: "F – Bereichsleitung / GF",
|
||
};
|
||
|
||
export function VertragTab({ employee }: { employee: EmployeeRow }) {
|
||
// Früher stand hier eine einzige Zeile „Merkmale" mit allem, was zutraf,
|
||
// durch Kommas getrennt — und ein Gedankenstrich, wenn nichts zutraf. Damit
|
||
// liess sich nicht ablesen, ob jemand *keinen* Dienstwagen hat oder ob
|
||
// niemand die Frage je beantwortet hat. Jedes Merkmal steht jetzt für sich,
|
||
// mit Ja oder Nein, wie jede andere Zeile auf diesem Blatt auch.
|
||
const rows: [string, string][] = [
|
||
["Eintrittsdatum", fmtDate(employee.entry_date)],
|
||
["Vertragsart", employee.contract_type === "befristet" ? `befristet bis ${fmtDate(employee.contract_end_date)}` : "unbefristet"],
|
||
["Kollektivvertrag", employee.collective_agreement ?? "–"],
|
||
["Beschäftigungsausmaß", employee.employment_type],
|
||
["Wochenstunden", `${employee.weekly_hours} h`],
|
||
["Urlaubsanspruch", "25 Tage"],
|
||
["Paygrade", PAYGRADE_LABELS[employee.paygrade] ?? employee.paygrade],
|
||
["Angestellte:r / Arbeiter:in", employee.worker_type ?? "–"],
|
||
["Arbeitstage", employee.work_days?.join(", ") || "–"],
|
||
// Beim Dienstwagen steht die Antriebsart statt eines blossen „Ja" — das
|
||
// war die Frage dahinter, seit E-Fahrzeuge getrennt zu führen sind.
|
||
["Dienstwagen", employee.has_dienstwagen ? dienstwagenLabel(employee.dienstwagen_art) : "Nein"],
|
||
["Betriebsrat", employee.is_betriebsrat ? "Ja" : "Nein"],
|
||
["Laterale Führung", employee.is_laterale_fuehrung ? "Ja" : "Nein"],
|
||
["C-Level", employee.is_c_level ? "Ja" : "Nein"],
|
||
// Das Enddatum steht gleich dabei: „Ja" allein liesse offen, ob der
|
||
// Schutz noch läuft, und genau danach fragt man.
|
||
// Die Teilzeitvariante gehört neben die Stunden: sie erklärt, warum sie
|
||
// sind, wie sie sind.
|
||
[
|
||
"Teilzeitvariante",
|
||
employee.teilzeit_art
|
||
? employee.teilzeit_bis
|
||
? `${employee.teilzeit_art} bis ${fmtDate(employee.teilzeit_bis)}`
|
||
: `${employee.teilzeit_art} (Ende offen)`
|
||
: "–",
|
||
],
|
||
[
|
||
"Besonderer Kündigungsschutz",
|
||
employee.has_kuendigungsschutz
|
||
? employee.kuendigungsschutz_bis
|
||
? `bis ${fmtDate(employee.kuendigungsschutz_bis)}`
|
||
: "Ja (Ende offen)"
|
||
: "Nein",
|
||
],
|
||
];
|
||
if (employee.exit_date) rows.push(["Austrittsdatum", fmtDate(employee.exit_date)]);
|
||
|
||
return (
|
||
<dl className="grid grid-cols-1 gap-x-8 gap-y-4 sm:grid-cols-2 lg:grid-cols-3">
|
||
{rows.map(([label, value]) => (
|
||
<div key={label}>
|
||
<dt className="text-xs font-semibold uppercase tracking-wide text-ink-muted">{label}</dt>
|
||
<dd className="mt-1 text-sm text-ink">{value}</dd>
|
||
</div>
|
||
))}
|
||
</dl>
|
||
);
|
||
}
|