Restructures into apps/ssp + apps/behandelportal (two Angular projects) plus libs/shared + libs/beheer (cross-app libraries), replacing WP-61's separate sibling repo. That split had already produced real drift: a hand-vendored copy of the backend's OpenAPI doc, a shared/ui+layout tree forked and silently diverging (7 files), and beheer + the styles.scss token bridge duplicated byte-for-byte across both repos. - git mv the SSP's src/app/* into apps/ssp/; fold shared/, beheer/, environments/, the Storybook docs/*.mdx, and styles.scss into libs/shared + libs/beheer (all confirmed identical between the two repos before merging). auth stays deliberately duplicated per ADR-0002 (actor-specific, expected to diverge) - amended there. - One generated API client (libs/shared), no more vendored swagger.json. - .dependency-cruiser split into a base factory + one config per app, and Storybook into .storybook-ssp/.storybook-behandelportal - both forced by the @auth/* alias resolving to different directories per app. - SiteHeaderComponent/ShellComponent gained HEADER_NAV_ITEMS/ HEADER_ADMIN_LINKS/DEBUG_PANEL injection tokens so each app supplies its own nav/admin-links/dev-panel instead of one being hardcoded. - CLAUDE.md, ARCHITECTURE.md, dependencies.md, and ADR-0002 updated; WP-67 backlog entry documents the full decision trail. npm run ci green (lint, dep:check x2, 360 tests across ssp/ behandelportal/shared/beheer, both localized builds, backend tests, snippet + api-client drift); both dev servers, both Storybook instances, and docker compose verified working. The old sibling repo (/home/eho/repos/behandelportal) is left untouched, not deleted. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
60 lines
2.1 KiB
TypeScript
60 lines
2.1 KiB
TypeScript
/**
|
|
* WIRE CONTRACT for the dashboard screen — the "BFF-lite" response.
|
|
*
|
|
* PURE wire shapes: this file imports NOTHING (CLAUDE.md §1, ADR-0001). Enums are
|
|
* inlined string-literal unions that describe the wire, not the domain. The
|
|
* adapter's `parseDashboardView` validates this untrusted shape and MAPS it onto
|
|
* the FE domain model (Registration/Person/BigProfile) — that map is the
|
|
* decoupling seam: the wire can change without the domain following.
|
|
*
|
|
* In production these types are GENERATED from the OpenAPI/TypeSpec spec (one
|
|
* source of truth for both sides), and the `decisions` block is computed BY THE
|
|
* BACKEND — never recomputed on the client. The frontend renders decisions; it
|
|
* does not own the rules. See docs/reference/architecture/0001-bff-lite-decision-dtos.md.
|
|
*
|
|
* One screen-shaped call replaces the previous three (BIG-register + BRP + …),
|
|
* so the page always sees one consistent snapshot instead of three independently
|
|
* loading/erroring resources.
|
|
*/
|
|
|
|
/** Registration status on the wire: the discriminant tags as they arrive. */
|
|
export type RegistrationStatusDto =
|
|
| { tag: 'Geregistreerd'; herregistratieDatum: string } // ISO date
|
|
| { tag: 'Geschorst'; geschorstTot: string; reden: string }
|
|
| { tag: 'Doorgehaald'; doorgehaaldOp: string; reden: string };
|
|
|
|
export interface RegistrationDto {
|
|
bigNummer: string;
|
|
naam: string;
|
|
beroep: string;
|
|
registratiedatum: string; // ISO date
|
|
geboortedatum: string;
|
|
status: RegistrationStatusDto;
|
|
}
|
|
|
|
export interface AdresDto {
|
|
straat: string;
|
|
postcode: string;
|
|
woonplaats: string;
|
|
}
|
|
|
|
export interface PersonDto {
|
|
naam: string;
|
|
geboortedatum: string; // ISO date
|
|
adres: AdresDto;
|
|
}
|
|
|
|
/** Server-computed decisions. Rendered by the FE as-is (decision DTO, ADR-0001):
|
|
the eligibility rule lives on the backend; the optional reason lets the UI
|
|
explain itself without knowing the rule. */
|
|
export interface HerregistratieDecisions {
|
|
eligibleForHerregistratie: boolean;
|
|
herregistratieReason?: string;
|
|
}
|
|
|
|
export interface DashboardViewDto {
|
|
registration: RegistrationDto;
|
|
person: PersonDto;
|
|
decisions: HerregistratieDecisions;
|
|
}
|