204 WP-NN/RB-NN comments named a closed ticket instead of the code they sit next to. git blame already records history and stays correct when code moves; the comment does not. This sweep removes the reference and keeps the sentence, across 95 files in apps/ and libs/ plus the behaviour-spec generator's header text. Eleven references stay: five story files justify an a11y disable per the README's rule, and one line in a11y.mdx documents that convention. Two sentences needed a rewrite, not a deletion, so the reference's meaning survives its removal. behaviour-spec.mdx is regenerated, not hand-edited. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
24 lines
958 B
TypeScript
24 lines
958 B
TypeScript
/**
|
|
* A queue entry as the behandelportal sees it — the parsed, domain-side view
|
|
* of the backend's cross-owner `GET /werkvoorraad`. Pure types, no Angular.
|
|
*
|
|
* The status union is narrower than the SSP's full `AanvraagStatus` (ssp's
|
|
* `registratie/domain/aanvraag.ts`): the backend only ever puts a case in the queue
|
|
* while it is still open (`Ingediend`/`InBehandeling`), so a queue item literally
|
|
* cannot be `Concept`/`Goedgekeurd`/`Afgewezen` — illegal states unrepresentable.
|
|
*/
|
|
export type AanvraagType = 'registratie' | 'herregistratie' | 'intake';
|
|
|
|
export type WerkvoorraadStatus =
|
|
| { tag: 'Ingediend'; referentie: string }
|
|
| { tag: 'InBehandeling'; referentie: string; manual: boolean };
|
|
|
|
export interface WerkvoorraadItem {
|
|
id: string;
|
|
type: AanvraagType;
|
|
status: WerkvoorraadStatus;
|
|
/** The BSN of the citizen the aanvraag belongs to — always populated (cross-owner list). */
|
|
owner: string;
|
|
submittedAt?: string;
|
|
}
|