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
2.1 KiB
TypeScript
72 lines
2.1 KiB
TypeScript
import type { EmploymentStatus, NoteCategory } from "./types";
|
|
|
|
const AVATAR_PALETTE = [
|
|
"#d6046e",
|
|
"#00666d",
|
|
"#5c2e91",
|
|
"#835b00",
|
|
"#0e700e",
|
|
"#b0035a",
|
|
"#2b6cb0",
|
|
"#a30354",
|
|
];
|
|
|
|
// Stable per-employee avatar color when employees.avatar_color isn't set.
|
|
export function avatarColorFor(seed: string): string {
|
|
let hash = 0;
|
|
for (let i = 0; i < seed.length; i++) {
|
|
hash = (hash << 5) - hash + seed.charCodeAt(i);
|
|
hash |= 0;
|
|
}
|
|
return AVATAR_PALETTE[Math.abs(hash) % AVATAR_PALETTE.length];
|
|
}
|
|
|
|
export const STATUS_STYLES: Record<EmploymentStatus, string> = {
|
|
Aktiv: "bg-success-bg text-success-text",
|
|
Karenz: "bg-warning-bg text-warning-text",
|
|
Geplant: "bg-brand-100 text-brand-700",
|
|
Ausgetreten: "bg-danger-bg text-danger-text",
|
|
};
|
|
|
|
type ColorCategory = "success" | "danger" | "warning" | "info" | "purple" | "brand";
|
|
|
|
export const CATEGORY_STYLES: Record<ColorCategory, string> = {
|
|
success: "bg-success-bg text-success-text",
|
|
danger: "bg-danger-bg text-danger-text",
|
|
warning: "bg-warning-bg text-warning-text",
|
|
info: "bg-info-bg text-info-text",
|
|
purple: "bg-purple-bg text-purple-text",
|
|
brand: "bg-brand-100 text-brand-700",
|
|
};
|
|
|
|
// Audit-log / activity-feed action -> badge color, per the action list in
|
|
// dem Kommentar an audit_log in der ersten Migration.
|
|
const ACTION_CATEGORY: Record<string, ColorCategory> = {
|
|
Neueinstellung: "success",
|
|
Wiedereinstellung: "success",
|
|
Rückkehr: "success",
|
|
Austritt: "danger",
|
|
Versetzung: "info",
|
|
Ausschreibung: "info",
|
|
"Interne Besetzung": "info",
|
|
Beförderung: "purple",
|
|
Reorganisation: "purple",
|
|
"Reorganisation rückgängig": "purple",
|
|
Karenz: "warning",
|
|
Vertragsänderung: "warning",
|
|
Stammdatenänderung: "warning",
|
|
Gehaltsanpassung: "warning",
|
|
};
|
|
|
|
export function actionBadgeStyle(action: string): string {
|
|
return CATEGORY_STYLES[ACTION_CATEGORY[action] ?? "brand"];
|
|
}
|
|
|
|
export const NOTE_CATEGORY_STYLES: Record<NoteCategory, string> = {
|
|
Vertraulich: CATEGORY_STYLES.purple,
|
|
"Personalgespräch": CATEGORY_STYLES.info,
|
|
Wiedervorlage: CATEGORY_STYLES.warning,
|
|
"Lob / Anerkennung": CATEGORY_STYLES.success,
|
|
Allgemein: "bg-surface text-ink-muted",
|
|
};
|