refactor: move the portal home into its own overzicht context (RD-03)

The dashboard page lived inside registratie, a context with no permitted outbound edges. Two of its sections do cross-context navigation: action links to herregistratie/intake/brief/concepts, and an admin links section that imported ADMIN_LINKS directly from the app shell. Move the page and these two navigation sections into a new overzicht context. Declare overzicht: ['registratie'] as the one sanctioned edge, so the four data sections that stay in registratie/ui/dashboard/ remain reachable. The route stays at /dashboard: it is a user-visible URL and four e2e specs assert it, so only the import path and class name change. beheer-links.section.ts now injects HEADER_ADMIN_LINKS, the same token the site header uses, instead of importing the app shell's nav config directly. Used npm run gen:context and corrected its three known-wrong outputs: the overzicht: [] edge, the scaffolded overzicht.page.ts (the real page is the moved dashboard.page.ts), and the scaffolded path: 'overzicht' route. Verified the boundary is enforced, not decorative: a temporary import of a herregistratie file into overzicht.page.ts makes dep:check fail, as expected, then reverted. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-04 16:26:11 +02:00
parent b9d572cfdc
commit b9fd411283
8 changed files with 187 additions and 13 deletions
@@ -0,0 +1,43 @@
+import { Component } from '@angular/core';
+import { PageShellComponent } from '@shared/layout/page-shell/page-shell.component';
+import { MijnAanvragenSection } from '@registratie/ui/dashboard/mijn-aanvragen.section';
+import { WatMoetIkRegelenSection } from '@registratie/ui/dashboard/wat-moet-ik-regelen.section';
+import { MijnRegistratieSection } from '@registratie/ui/dashboard/mijn-registratie.section';
+import { SpecialismenSection } from '@registratie/ui/dashboard/specialismen.section';
+import { WatWiltUDoenSection } from './wat-wilt-u-doen.section';
+import { BeheerLinksSection } from './beheer-links.section';
+
+/** Page: "Mijn overzicht" — the portal home, following the NL Design System "Mijn
+    omgeving" pattern. Composition only: each section below answers its own data
+    question (own store, own async state) — four sections stay in `registratie/ui/dashboard/`
+    (they render registratie data), two live here (cross-context navigation). */
+@Component({
+  selector: 'app-overzicht-page',
+  imports: [
+    PageShellComponent,
+    MijnAanvragenSection,
+    WatMoetIkRegelenSection,
+    MijnRegistratieSection,
+    SpecialismenSection,
+    WatWiltUDoenSection,
+    BeheerLinksSection,
+  ],
+  template: `
+    <app-page-shell
+      i18n-heading="@@dashboard.heading"
+      heading="Mijn overzicht"
+      i18n-intro="@@dashboard.intro"
+      intro="Welkom in uw persoonlijke omgeving van het BIG-register. Hier ziet u uw registratie en regelt u uw zaken."
+    >
+      <div class="app-stack">
+        <app-mijn-aanvragen-section />
+        <app-wat-moet-ik-regelen-section />
+        <app-mijn-registratie-section />
+        <app-specialismen-section />
+        <app-wat-wilt-u-doen-section />
+        <app-beheer-links-section />
+      </div>
+    </app-page-shell>
+  `,
+})
+export class OverzichtPage {}