8b8e9fee9c
Diffing what the lightweight packet ACTUALLY prints on each path against its card (map, triangle, profiles, wheel, points) found the wall path missing two pages and half of a third -- while the legend path matched. Same class as the sets page: the renderer could draw every page, and only one of the two hosts supplied the arguments. Three gaps, three suppliers: The map. printPacketAs passed no mapSvg and there was no default, so a wall-printed packet opened on a title-only cover. printPacket now lifts the bundle's own poster (posters/<id>.html, the same file printPoster already reads) when the host passes nothing -- via a liftPosterSvg helper shaped for unit-testing against a real generated poster, no fetch. Verified on laos: the svg is found and lifted. And PosterWall now actually passes assetsBase into its print opts; without that one line the lift's guard would skip silently and the wall would STILL print a mapless packet -- the seam-without-supplier failure one layer down, caught in the same pass. The triangle. No funnel was supplied and none defaulted. The default states ONLY the steps: listCount and unassigned stay absent, so funnelPage omits the share line and the tip rather than printing a denominator that is wrong under a non-default list. Proved two-sided: steps-only renders the triangle with no share claims; adding listCount renders both. The profiles. The wall's fetch carried primary_language but not imb_gsec, so every wall-printed description ran at half length -- the third fetch site with the same missing-field defect, found the same way. |
||
|---|---|---|
| .. | ||
| api | ||
| charts | ||
| colors | ||
| components | ||
| composables | ||
| constants | ||
| data | ||
| elements | ||
| i18n | ||
| layouts | ||
| lists | ||
| maps | ||
| packet | ||
| packets | ||
| scripts | ||
| stores | ||
| styles | ||
| utils | ||
| vendor/cldr | ||
| index.js | ||
| ProfileLoader.vue | ||
| README.md | ||
library/ (@map) — the shared map template
The other half of the architecture (see ../plugin-designs/README.md):
every map in plugin-designs/<your-map>/ composes the reusable, parameterized pieces that live here.
Fix something here and every map benefits on the next build; break something here and every map
breaks — read components/WARNING.md before touching shared pieces.
| Folder | What lives there |
|---|---|
ProfileLoader.vue |
The root of every bundle: parses profile-config, loads the profile, provides the stores + config |
components/ |
Shared UI — map, legends, controls, popup (PeopleGroupDetail), tables, charts, hints (README) |
composables/ |
Shared logic — map engine (useMapInstance), provider switch, shadow-DOM styles, theming |
stores/ |
Per-instance Pinia stores (ui / map / data) — provided by ProfileLoader, injected by children |
api/ |
Data-source registry (sources.json) + fetch layer — the JAMstack runtime wiring |
colors/ |
Color sets maps opt into via profile-config.colorSet |
i18n/ |
The shared string catalogs (all maps speak the same languages) |
data/ |
Small shared datasets baked at build time (big served data lives in ../data/) |
constants/ |
Shared constants |
scripts/ |
Maintainer pipelines (posters, research) — not part of any bundle |
The rule of thumb (same as WARNING.md): custom code in your app-profile, reusable code here — and things only move from the first to the second once they've earned it.