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>
61 lines
2.3 KiB
TypeScript
61 lines
2.3 KiB
TypeScript
import { SelectField, TextField } from "@/components/ui/Field";
|
|
import { EMERGENCY_RELATIONS } from "@/lib/types";
|
|
import type { HireDraftData } from "./types";
|
|
|
|
// Eigener Schritt, kurz vor der Zusammenfassung.
|
|
//
|
|
// Zuerst stand das zwischen den Stammdaten — dort ging es unter, obwohl es
|
|
// die einzige Angabe im ganzen Assistenten ist, die eine dritte Person
|
|
// betrifft und im Ernstfall gebraucht wird.
|
|
//
|
|
// Die Angabe bleibt freiwillig. Wer sie macht, braucht Name und Nummer
|
|
// zusammen; das prüft der Assistent, bevor er weiterlässt, und die Datenbank
|
|
// noch einmal (chk_emergency_contact).
|
|
export function StepNotfallkontakt({
|
|
draft,
|
|
update,
|
|
}: {
|
|
draft: HireDraftData;
|
|
update: (patch: Partial<HireDraftData>) => void;
|
|
}) {
|
|
const angefangen = Boolean(draft.emergencyContactName.trim() || draft.emergencyContactPhone.trim());
|
|
const unvollstaendig = angefangen && !(draft.emergencyContactName.trim() && draft.emergencyContactPhone.trim());
|
|
|
|
return (
|
|
<div className="flex flex-col gap-4">
|
|
<p className="max-w-prose text-sm text-ink-muted">
|
|
Wen sollen wir verständigen, wenn etwas passiert? Die Angabe ist freiwillig — Name und Telefonnummer gehören
|
|
aber zusammen, eines allein hilft im Ernstfall nicht.
|
|
</p>
|
|
|
|
<div className="grid grid-cols-1 gap-3 sm:grid-cols-2">
|
|
<TextField
|
|
label="Name"
|
|
value={draft.emergencyContactName}
|
|
onChange={(emergencyContactName) => update({ emergencyContactName })}
|
|
/>
|
|
<TextField
|
|
label="Telefon"
|
|
type="tel"
|
|
value={draft.emergencyContactPhone}
|
|
onChange={(emergencyContactPhone) => update({ emergencyContactPhone })}
|
|
/>
|
|
</div>
|
|
|
|
<SelectField
|
|
label="Verhältnis"
|
|
value={draft.emergencyContactRelation}
|
|
onChange={(emergencyContactRelation) => update({ emergencyContactRelation })}
|
|
placeholder="Bitte wählen…"
|
|
options={EMERGENCY_RELATIONS.map((r) => ({ value: r, label: r }))}
|
|
/>
|
|
|
|
{unvollstaendig && (
|
|
<p role="alert" className="rounded-md border border-danger-text/20 bg-danger-bg px-3 py-2 text-sm text-danger-text">
|
|
Name und Telefonnummer werden beide gebraucht — oder beide leer lassen.
|
|
</p>
|
|
)}
|
|
</div>
|
|
);
|
|
}
|