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>
79 lines
2.9 KiB
TypeScript
79 lines
2.9 KiB
TypeScript
import type { EmploymentStatus } from "./types";
|
|
|
|
// Langzeitabwesenheit.
|
|
//
|
|
// The database still stores the employment status as 'Karenz' — renaming an
|
|
// enum value would mean rewriting every stored function that spells it, for
|
|
// a label change (see db/migrations/*_absence_type.sql). So the value
|
|
// is mapped to its display name here, in the one place the UI reads it from.
|
|
|
|
// Nur echte Abwesenheiten. Eine Teilzeit ist keine: wer in Bildungs-,
|
|
// Pflege-, Eltern- oder Wiedereingliederungsteilzeit ist, arbeitet — nur
|
|
// weniger. Als „Langzeitabwesenheit" geführt, verschwand die Person aus dem
|
|
// Bestand, verlor ihre Berichtslinie an eine Vertretung und zählte in
|
|
// Auswertungen nicht mehr mit, obwohl sie jede Woche im Haus war.
|
|
//
|
|
// Die vier sind deshalb hierher gewandert, wo sie hingehören: zur
|
|
// Stundenänderung (siehe STUNDEN_GRUENDE) und zur Rückkehr aus einer
|
|
// Abwesenheit (RUECKKEHR_GRUENDE).
|
|
export const ABSENCE_TYPES = [
|
|
"Wochenhilfe (Mutterschutz)",
|
|
"Elternkarenz (inkl. Väterkarenz)",
|
|
"Papamonat",
|
|
"Bildungskarenz",
|
|
"Präsenzdienst",
|
|
"Zivildienst",
|
|
"Langer Krankenstand",
|
|
"Pflegekarenz",
|
|
"Familienhospizkarenz",
|
|
"Sabbatical",
|
|
] as const;
|
|
|
|
export type AbsenceType = (typeof ABSENCE_TYPES)[number];
|
|
|
|
export function isAbsenceType(value: string | null | undefined): value is AbsenceType {
|
|
return ABSENCE_TYPES.includes(value as AbsenceType);
|
|
}
|
|
|
|
/**
|
|
* Warum jemand nach einer Abwesenheit mit weniger Stunden zurückkommt.
|
|
*
|
|
* Beides sind Ansprüche, keine freien Vereinbarungen — und beide beginnen
|
|
* typischerweise genau dann, wenn die Abwesenheit endet.
|
|
*/
|
|
export const RUECKKEHR_GRUENDE = ["Wiedereingliederungsteilzeit", "Elternteilzeit"] as const;
|
|
|
|
/**
|
|
* Warum sich die Wochenstunden ändern.
|
|
*
|
|
* Der erste Wert ist der Normalfall; die beiden anderen sind gesetzlich
|
|
* geregelte Teilzeiten, die man später wiederfinden können muss — im
|
|
* Zweifel Jahre danach, wenn jemand fragt, warum die Stunden damals sanken.
|
|
*/
|
|
export const STUNDEN_GRUENDE = ["Vertragliche Stundenänderung", "Bildungsteilzeit", "Pflegeteilzeit"] as const;
|
|
|
|
export type StundenGrund = (typeof STUNDEN_GRUENDE)[number];
|
|
|
|
/** Display names for the stored status values. */
|
|
const STATUS_LABELS: Record<EmploymentStatus, string> = {
|
|
Aktiv: "Aktiv",
|
|
Karenz: "Langzeitabwesenheit",
|
|
Geplant: "Geplant",
|
|
Ausgetreten: "Ausgetreten",
|
|
};
|
|
|
|
export function statusLabel(status: EmploymentStatus): string {
|
|
return STATUS_LABELS[status] ?? status;
|
|
}
|
|
|
|
/**
|
|
* The chip and the detail header show the specific kind when it is known —
|
|
* "Bildungskarenz" says more than "Langzeitabwesenheit". Absences recorded
|
|
* before the type existed have none, and fall back to the generic name
|
|
* rather than to a guess.
|
|
*/
|
|
export function absenceLabel(status: EmploymentStatus, absenceType: string | null | undefined): string {
|
|
if (status !== "Karenz") return statusLabel(status);
|
|
return isAbsenceType(absenceType) ? absenceType : STATUS_LABELS.Karenz;
|
|
}
|