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>
52 lines
2.0 KiB
TypeScript
52 lines
2.0 KiB
TypeScript
import { Injectable } from '@angular/core';
|
|
import { Result, ok, err } from '@shared/kernel/fp';
|
|
import { currentRole } from '@shared/infrastructure/role';
|
|
import { problemDetail } from '@shared/infrastructure/api-error';
|
|
import { environment } from '@shared/environments/environment';
|
|
|
|
const REVEAL_FAILED = $localize`:@@brief.reveal.failed:Het BIG-nummer kon niet worden getoond.`;
|
|
|
|
/**
|
|
* Field-level PII reveal (PRD-0002 §5c). The case screen ships the BIG-nummer masked;
|
|
* this unmasks it, gated server-side by the reveal capability AND a step-up. The
|
|
* step-up is stubbed as the `X-Step-Up` header — the caller sends it only after the
|
|
* user's confirm gesture, so a plain call (or a role without the capability) 403s.
|
|
*
|
|
* Hand-written fetch (not the `ApiClient`) because the call needs a per-request header;
|
|
* `.ExcludeFromDescription()` on the endpoint keeps the generated client JSON-only, the
|
|
* same seam as `/brief/preview` and uploads — which also means `X-Role` is set here.
|
|
*/
|
|
@Injectable({ providedIn: 'root' })
|
|
export class RevealBigNummerAdapter {
|
|
async reveal(): Promise<Result<string, string>> {
|
|
let res: Response;
|
|
try {
|
|
res = await fetch(`${environment.apiBaseUrl}/api/v1/brief/reveal-bignummer`, {
|
|
method: 'POST',
|
|
headers: { 'X-Role': currentRole(), 'X-Step-Up': 'true' },
|
|
});
|
|
} catch {
|
|
return err(REVEAL_FAILED);
|
|
}
|
|
if (!res.ok) return err(await errorMessage(res));
|
|
const body: unknown = await res.json().catch(() => null);
|
|
// Trust boundary: validate the shape before handing back a plain string.
|
|
if (
|
|
typeof body === 'object' &&
|
|
body !== null &&
|
|
typeof (body as { bigNummer?: unknown }).bigNummer === 'string'
|
|
) {
|
|
return ok((body as { bigNummer: string }).bigNummer);
|
|
}
|
|
return err(REVEAL_FAILED);
|
|
}
|
|
}
|
|
|
|
async function errorMessage(res: Response): Promise<string> {
|
|
try {
|
|
return problemDetail(await res.json(), REVEAL_FAILED);
|
|
} catch {
|
|
return REVEAL_FAILED;
|
|
}
|
|
}
|