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>
116 lines
3.9 KiB
TypeScript
116 lines
3.9 KiB
TypeScript
"use client";
|
|
|
|
import { useRouter } from "next/navigation";
|
|
import { useState } from "react";
|
|
import { addEmployeeDependent } from "@/actions/employees";
|
|
import { Button } from "@/components/ui/Button";
|
|
import { SelectField, TextField } from "@/components/ui/Field";
|
|
import { Modal } from "@/components/ui/Modal";
|
|
import { useToast } from "@/components/ui/Toast";
|
|
import { todayIso } from "@/lib/format";
|
|
import type { RelationshipType } from "@/lib/types";
|
|
|
|
const RELATIONSHIPS: RelationshipType[] = ["Ehepartner:in", "Lebenspartner:in", "Kind", "Sonstige"];
|
|
|
|
export function AddDependentModal({
|
|
open,
|
|
onClose,
|
|
employeeId,
|
|
defaultEffectiveDate,
|
|
}: {
|
|
open: boolean;
|
|
onClose: () => void;
|
|
employeeId: string;
|
|
defaultEffectiveDate?: string;
|
|
}) {
|
|
const { showToast } = useToast();
|
|
const router = useRouter();
|
|
const [firstName, setFirstName] = useState("");
|
|
const [lastName, setLastName] = useState("");
|
|
const [svNummer, setSvNummer] = useState("");
|
|
const [birthDate, setBirthDate] = useState("");
|
|
const [relationship, setRelationship] = useState<RelationshipType>("Kind");
|
|
const [effectiveDate, setEffectiveDate] = useState(defaultEffectiveDate ?? todayIso());
|
|
const [prevDefaultEffectiveDate, setPrevDefaultEffectiveDate] = useState(defaultEffectiveDate);
|
|
const [pending, setPending] = useState(false);
|
|
|
|
// This modal stays mounted while closed, so a mount-time initializer would
|
|
// pin the date forever: DatenAendernPanel drives `defaultEffectiveDate` off
|
|
// its own "Wirksam ab" field, and changing it there has to reach the field
|
|
// below. Same adjust-during-render pattern as CountryPicker.
|
|
if (defaultEffectiveDate !== prevDefaultEffectiveDate) {
|
|
setPrevDefaultEffectiveDate(defaultEffectiveDate);
|
|
if (defaultEffectiveDate) setEffectiveDate(defaultEffectiveDate);
|
|
}
|
|
|
|
function reset() {
|
|
setFirstName("");
|
|
setLastName("");
|
|
setSvNummer("");
|
|
setBirthDate("");
|
|
setRelationship("Kind");
|
|
setEffectiveDate(defaultEffectiveDate ?? todayIso());
|
|
}
|
|
|
|
async function handleSubmit() {
|
|
if (!firstName || !lastName || !birthDate || !effectiveDate) {
|
|
showToast("Bitte alle Pflichtfelder ausfüllen.", "error");
|
|
return;
|
|
}
|
|
setPending(true);
|
|
const result = await addEmployeeDependent({
|
|
employee_id: employeeId,
|
|
first_name: firstName,
|
|
last_name: lastName,
|
|
relationship,
|
|
sv_nummer: svNummer || undefined,
|
|
birth_date: birthDate,
|
|
effective_date: effectiveDate,
|
|
});
|
|
setPending(false);
|
|
if (result.success) {
|
|
showToast("Angehörige:r hinzugefügt.");
|
|
router.refresh();
|
|
onClose();
|
|
reset();
|
|
} else {
|
|
showToast(result.error ?? "Fehler beim Speichern.", "error");
|
|
}
|
|
}
|
|
|
|
return (
|
|
<Modal
|
|
open={open}
|
|
onClose={onClose}
|
|
title="Angehörige:n hinzufügen"
|
|
footer={
|
|
<>
|
|
<Button variant="ghost" onClick={onClose}>
|
|
Abbrechen
|
|
</Button>
|
|
<Button onClick={handleSubmit} pending={pending}>
|
|
Hinzufügen
|
|
</Button>
|
|
</>
|
|
}
|
|
>
|
|
<div className="flex flex-col gap-4">
|
|
<TextField label="Wirksam ab" required type="date" value={effectiveDate} onChange={setEffectiveDate} />
|
|
<div className="grid grid-cols-1 gap-3 sm:grid-cols-2">
|
|
<TextField label="Vorname" required value={firstName} onChange={setFirstName} />
|
|
<TextField label="Nachname" required value={lastName} onChange={setLastName} />
|
|
</div>
|
|
<TextField label="SVNR" inputMode="numeric" value={svNummer} onChange={setSvNummer} />
|
|
<TextField label="Geburtsdatum" required type="date" value={birthDate} onChange={setBirthDate} />
|
|
<SelectField
|
|
label="Verwandtschaftsverhältnis"
|
|
required
|
|
value={relationship}
|
|
onChange={(v) => setRelationship(v as RelationshipType)}
|
|
options={RELATIONSHIPS.map((r) => ({ value: r, label: r }))}
|
|
/>
|
|
</div>
|
|
</Modal>
|
|
);
|
|
}
|