5725f5b9d9
Some checks are pending
build-gate / build (push) Waiting to run
stack-demo rendered two empty sections in dev. Its sibling bundles were addressed with a tree-relative path, which the browser resolves against the document URL, so no host and no attribute can redirect it — correct in the built tree, a 404 in dev. Measured: the dev entry answers 200 while the path the relative form resolves to answers 404. The sources now resolve at runtime, so the same file is right in both trees, and the production branch compiles away to the string it replaces. That was the third place this defect appeared. Both capability-5 shells carried the same hardcoded paths and were cured the same way, and each instance was found separately after the previous one was fixed — because a literal parent-directory path reads as correct in review and is invisible to a gate that only ever checks the built tree. Removing the 404 was not enough: the sections were still empty with zero failed requests. The shared layout injected each bundle with a classic script, and a classic script pointed at a dev ES module fires its load handler successfully and only then throws, so the promise resolved while the tag never registered and the wait for definition quietly timed out. A load handler cannot detect that. The module rule now lives in the shared layout rather than in a fourth private copy of the same loader, so the two other composites that inject through it are covered too. Verified after: both elements define, sixty-six facet rows and twenty-four cards on stack-demo and on dashboard-plus-grid, zero failed requests on each. |
||
|---|---|---|
| .. | ||
| app-wrapper-material | ||
| pane-wrapper | ||
| README.md | ||
| StackLayout.vue | ||
| VerticalTabsLayout.vue | ||
layouts/ — app wrappers
Each folder here is an app wrapper: a host shell that composes doxa-maps plugin-designs (the independently-built custom elements) into one application.
layouts/<wrapper>/ ← the HOST page (not a bundle)
┌──────────┬──────────────────────────────┐
│ sidebar │ mounts an app-profile here │
│ (nav.js) │ ┌──────────────┐ │
│ ├ item │ │ <doxa-map> │ ← a │
│ ├ section│ │ (a bundle) │ micro- │
│ └ folder │ └──────────────┘ frontend │
└──────────┴──────────────────────────────┘
- app-profile = a self-contained custom element (the micro-frontend). app wrapper = the host that mounts them and provides nav/chrome. A wrapper is a host page, not a bundle-in-a-bundle.
- Wrappers today:
app-wrapper-material/,pane-wrapper/. - Icons are inline SVG only (no CDN) — an F-Droid/offline hard requirement.
Sidebar contract, target filtering, sidebar modes, staging: ../documentation/architecture/app-wrappers.md.