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>
146 lines
5.9 KiB
TypeScript
146 lines
5.9 KiB
TypeScript
"use client";
|
|
|
|
import { SelectField, TextField } from "@/components/ui/Field";
|
|
import type { CollectiveAgreement, DienstwagenArt, Weekday, WorkerType } from "@/lib/types";
|
|
|
|
const WEEKDAYS: Weekday[] = ["Mo", "Di", "Mi", "Do", "Fr", "Sa", "So"];
|
|
|
|
export type RoleEmploymentValue = {
|
|
workerType: WorkerType;
|
|
collectiveAgreement: CollectiveAgreement;
|
|
workDays: Weekday[];
|
|
isBetriebsrat: boolean;
|
|
hasDienstwagen: boolean;
|
|
/**
|
|
* Nur bedeutsam, solange hasDienstwagen gesetzt ist.
|
|
*
|
|
* Der Wert bleibt beim Abwählen stehen, statt zurückgesetzt zu werden —
|
|
* wer versehentlich klickt und zurückklickt, findet seine Angabe wieder.
|
|
* Beim Speichern setzen die Aufrufer ihn auf null, wie es der CHECK
|
|
* verlangt.
|
|
*/
|
|
dienstwagenArt: DienstwagenArt;
|
|
isLateraleFuehrung: boolean;
|
|
isCLevel: boolean;
|
|
/** Betriebsrat, Mutterschutz, Karenz, begünstigte Behinderung, Lehre. */
|
|
hasKuendigungsschutz: boolean;
|
|
/**
|
|
* Ende des Schutzes — freiwillig. Bei einem Betriebsratsmandat steht es
|
|
* fest, bei einer Schwangerschaft nicht; ein Pflichtfeld zwänge dort zu
|
|
* einer erfundenen Zahl. Leer heisst „bis auf Weiteres".
|
|
*/
|
|
kuendigungsschutzBis: string;
|
|
};
|
|
|
|
// Shared by the hire wizard (StepVertrag) and DatenAendernPanel — both edit
|
|
// the same set of employees columns, just against different local state.
|
|
export function RoleEmploymentFields({ value, onChange }: { value: RoleEmploymentValue; onChange: (patch: Partial<RoleEmploymentValue>) => void }) {
|
|
function toggleWorkDay(day: Weekday) {
|
|
onChange({ workDays: value.workDays.includes(day) ? value.workDays.filter((d) => d !== day) : [...value.workDays, day] });
|
|
}
|
|
|
|
return (
|
|
<div className="flex flex-col gap-3">
|
|
<div className="grid grid-cols-1 gap-3 sm:grid-cols-2">
|
|
<SelectField
|
|
label="Angestellte:r / Arbeiter:in"
|
|
dense
|
|
value={value.workerType}
|
|
onChange={(v) => onChange({ workerType: v as WorkerType })}
|
|
options={[
|
|
{ value: "Angestellte:r", label: "Angestellte:r" },
|
|
{ value: "Arbeiter:in", label: "Arbeiter:in" },
|
|
]}
|
|
/>
|
|
<SelectField
|
|
label="Kollektivvertrag"
|
|
dense
|
|
value={value.collectiveAgreement}
|
|
onChange={(v) => onChange({ collectiveAgreement: v as CollectiveAgreement })}
|
|
options={[
|
|
{ value: "Handel", label: "Handel" },
|
|
{ value: "Süßwaren", label: "Süßwaren" },
|
|
]}
|
|
/>
|
|
</div>
|
|
|
|
{/* Toggle group, not a set of fields: a fieldset names the group, and
|
|
aria-pressed is what tells a screen reader a day is selected —
|
|
colour alone does not. */}
|
|
<fieldset>
|
|
<legend className="mb-1 block text-xs font-semibold text-ink-muted">Arbeitstage</legend>
|
|
<div className="flex flex-wrap gap-1.5">
|
|
{WEEKDAYS.map((day) => (
|
|
<button
|
|
key={day}
|
|
type="button"
|
|
aria-pressed={value.workDays.includes(day)}
|
|
onClick={() => toggleWorkDay(day)}
|
|
className={`rounded-full px-3 py-1.5 text-xs font-semibold focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-brand-500 ${
|
|
value.workDays.includes(day) ? "bg-brand-500 text-white" : "border border-border text-ink-muted hover:bg-surface"
|
|
}`}
|
|
>
|
|
{day}
|
|
</button>
|
|
))}
|
|
</div>
|
|
</fieldset>
|
|
|
|
<div className="flex flex-col gap-2">
|
|
<label className="flex items-center gap-2 text-sm text-ink-body">
|
|
<input type="checkbox" checked={value.isBetriebsrat} onChange={(e) => onChange({ isBetriebsrat: e.target.checked })} />
|
|
Betriebsrat
|
|
</label>
|
|
<label className="flex items-center gap-2 text-sm text-ink-body">
|
|
<input type="checkbox" checked={value.hasDienstwagen} onChange={(e) => onChange({ hasDienstwagen: e.target.checked })} />
|
|
Dienstwagen
|
|
</label>
|
|
{/* Nur sichtbar, wenn es einen gibt: eine Antriebsart ohne Fahrzeug
|
|
ist keine Angabe, sondern eine Frage ohne Gegenstand — und die
|
|
Datenbank weist sie ab. */}
|
|
{value.hasDienstwagen && (
|
|
<SelectField
|
|
label="Antriebsart"
|
|
dense
|
|
value={value.dienstwagenArt}
|
|
onChange={(v) => onChange({ dienstwagenArt: v as DienstwagenArt })}
|
|
options={[
|
|
{ value: "Verbrenner", label: "Verbrenner" },
|
|
{ value: "Elektro", label: "Elektro (E-KFZ)" },
|
|
]}
|
|
/>
|
|
)}
|
|
<label className="flex items-center gap-2 text-sm text-ink-body">
|
|
<input type="checkbox" checked={value.isLateraleFuehrung} onChange={(e) => onChange({ isLateraleFuehrung: e.target.checked })} />
|
|
Laterale Führung
|
|
</label>
|
|
<label className="flex items-center gap-2 text-sm text-ink-body">
|
|
<input type="checkbox" checked={value.isCLevel} onChange={(e) => onChange({ isCLevel: e.target.checked })} />
|
|
C-Level
|
|
</label>
|
|
<label className="flex items-center gap-2 text-sm text-ink-body">
|
|
<input
|
|
type="checkbox"
|
|
checked={value.hasKuendigungsschutz}
|
|
onChange={(e) => onChange({ hasKuendigungsschutz: e.target.checked })}
|
|
/>
|
|
Besonderer Kündigungsschutz
|
|
</label>
|
|
{/* Wie bei der Antriebsart: erst sichtbar, wenn es einen Gegenstand
|
|
gibt. Anders als dort aber freiwillig — leer heisst „bis auf
|
|
Weiteres", nicht „vergessen". */}
|
|
{value.hasKuendigungsschutz && (
|
|
<TextField
|
|
label="Geschützt bis"
|
|
dense
|
|
type="date"
|
|
value={value.kuendigungsschutzBis}
|
|
onChange={(v) => onChange({ kuendigungsschutzBis: v })}
|
|
hint="Optional. Leer lassen, solange das Ende nicht feststeht."
|
|
/>
|
|
)}
|
|
</div>
|
|
</div>
|
|
);
|
|
}
|