Maximilian Stubhan
f91a69147e
- components/hire/: 4-step Hire Wizard (Person/Position/Vertrag/ Zusammenfassung) matching sec4.4, with a HireWizardProvider context so it can be opened both from the global "+ Neueinstellung" button and from a "Fortsetzen" link on a saved draft. - actions/hireDrafts.ts: save/delete hire_drafts (owner-scoped RLS already in place from Phase 1). Dashboard now shows the "Entwuerfe" card the Phase 1 plan deferred, since the wizard it depends on now exists. - lib/positions.ts: shared open-positions loader (position number, org breadcrumb, resolved manager name) used by both the wizard and (later) the Positions page. Two real bugs found via live testing and fixed in supabase/functions.sql: 1. hire_employee/rehire_employee: a two-branch CASE returning bare string literals defaults to `text`, not the target enum, so `status = case when ... then 'Geplant' else 'Aktiv' end` failed against the employment_status column. Fixed with an explicit ::employment_status cast on the whole CASE expression. 2. Postgres precedence gotcha: ->> and || sit at the *same* precedence tier and left-associate, so `payload->>'first_name' || ' ' || payload->>'last_name'` does not group the way it reads - it tries to apply ->> to an intermediate text value and fails with "operator does not exist: text ->> unknown". Fixed by parenthesizing every ->>'...' expression that participates in a || chain. Also fixed: hire_employee referenced v_position.title outside the branch that assigns v_position, raising "record not assigned" whenever a hire wasn't tied to a position_id; extracted a v_job_title variable instead. Verified live end-to-end: wizard search -> select position -> submit creates the employee, closes the position, and writes matching employee_history + audit_log rows atomically.
41 lines
1.6 KiB
TypeScript
41 lines
1.6 KiB
TypeScript
import type { SupabaseClient } from "@supabase/supabase-js";
|
|
import { breadcrumbLabel, loadOrgMaps } from "./org";
|
|
import type { Database } from "./supabase/types";
|
|
|
|
export type OpenPositionResolved = {
|
|
id: string;
|
|
position_number: string;
|
|
title: string;
|
|
team_id: string;
|
|
division_id: string;
|
|
is_lead: boolean;
|
|
reports_to_employee_id: string | null;
|
|
created_at: string;
|
|
managerName: string | null;
|
|
orgLabel: string;
|
|
};
|
|
|
|
// Shared by the Hire Wizard (position lookup) and the Positions & Bereiche page.
|
|
export async function loadOpenPositions(supabase: SupabaseClient<Database>): Promise<OpenPositionResolved[]> {
|
|
const orgMaps = await loadOrgMaps(supabase);
|
|
const { data: positions } = await supabase
|
|
.from("positions")
|
|
.select("id, position_number, title, team_id, division_id, is_lead, reports_to_employee_id, created_at")
|
|
.eq("status", "open")
|
|
.order("created_at", { ascending: false });
|
|
|
|
const managerIds = Array.from(
|
|
new Set((positions ?? []).map((p) => p.reports_to_employee_id).filter((id): id is string => Boolean(id)))
|
|
);
|
|
const { data: managers } = managerIds.length
|
|
? await supabase.from("employees_directory").select("id, first_name, last_name").in("id", managerIds)
|
|
: { data: [] as { id: string; first_name: string; last_name: string }[] };
|
|
const managerNameById = new Map((managers ?? []).map((m) => [m.id, `${m.first_name} ${m.last_name}`]));
|
|
|
|
return (positions ?? []).map((p) => ({
|
|
...p,
|
|
managerName: p.reports_to_employee_id ? (managerNameById.get(p.reports_to_employee_id) ?? null) : null,
|
|
orgLabel: breadcrumbLabel(orgMaps, p.division_id, p.team_id),
|
|
}));
|
|
}
|