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. |
||
|---|---|---|
| .. | ||
| charts | ||
| dashboards | ||
| hints | ||
| legends | ||
| map-controls | ||
| poster | ||
| qa | ||
| regions | ||
| search | ||
| tables | ||
| BackToTopButton.vue | ||
| PeopleGroupDetail.vue | ||
| README.md | ||
| ResearchMapFilterPanel.vue | ||
| ResearchMapSideMenu.vue | ||
| SideMenuDrawer.vue | ||
| ViewSelect.vue | ||
| WARNING.md | ||
library/components/ — shared Vue components
The map UI, built from parameterized pieces every app-profile reuses. Fix one here and every map benefits — never edit a shared component to customize one map.
library/components/
┌───────────────────────────────────────────┐
│ legends/ map-controls/ poster/ │
│ charts/ tables/ │
│ PeopleGroupDetail.vue SideMenuDrawer.vue │
│ ResearchMapFilterPanel.vue …SideMenu.vue │
└───────────────────────────────────────────┘
reused by every app-profile via @map/components/…
legends/,map-controls/,poster/each have their own README.- Every component uses
<script setup>, callsuseShadowStyles(), and reaches stores viainject('mapStore' | 'uiStore' | 'dataStore')— never a direct store import.
Full catalog + conventions:
../../documentation/architecture/components.md ·
per-file roles: ../../documentation/reference.md.