ehoandClaude Sonnet 5
e7156c5132
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>
25 lines
965 B
TypeScript
25 lines
965 B
TypeScript
import { RemoteData } from '@shared/application/remote-data';
|
|
|
|
/** The standard load-lifecycle tags an editor machine exposes. */
|
|
export type LoadLifecycle =
|
|
{ tag: 'loading' } | { tag: 'failed'; reason: string } | { tag: 'loaded' };
|
|
|
|
/**
|
|
* Project an Elm-machine state onto `RemoteData` for the `<app-async>` seam. The machine
|
|
* keeps owning its own domain lifecycle (draft/submitted/…); this is purely the
|
|
* loading/failed/loaded → async mapping, which was byte-identical across BriefStore,
|
|
* OrgTemplateStore and StamdataStore (WP-31). Wrap the call in a `computed`.
|
|
*/
|
|
export function machineRemoteData<S extends LoadLifecycle>(
|
|
s: S,
|
|
): RemoteData<Error, Extract<S, { tag: 'loaded' }>> {
|
|
switch (s.tag) {
|
|
case 'loading':
|
|
return { tag: 'Loading' };
|
|
case 'failed':
|
|
return { tag: 'Failure', error: new Error(s.reason) };
|
|
default: // 'loaded'
|
|
return { tag: 'Success', value: s as Extract<S, { tag: 'loaded' }> };
|
|
}
|
|
}
|