ef439a5d8e
The print-time files are pinned (poster-render.js and its classic copy, packet-strings.json, ne-places.json, india-states.json) and were fetched with cache: 'force-cache', which returns any cached copy, however old. After a re-pin, a reader who had printed before kept the previous copy: it failed its pin on every print and the print fell back without a word. Page 1 became the stored poster, a non-English packet would print in English, and India's state cards would be lost. sha384.js fetchPinned fetches force-cache first (fast, and offline once cached) and, when the copy is not served or fails its pin, once more with cache: 'reload', which skips and refreshes the HTTP cache; only that answer decides. posterSheets (the generator and the places table), packetStrings and indiaStates all fetch through it. The classic-script path refreshes the cache the same way and retries a refused tag once. check:pinned-fetch-fresh models the HTTP cache with stale copies: page 1 still draws, the packet keeps every language, India keeps its 36 states; a matching cached copy is used with one request; wrong bytes are refused. The previous loaders fail it. Self-test poisons: no fresh refetch, never the cache, a mismatch accepted, a loader fetching its pinned file directly. |
||
|---|---|---|
| .. | ||
| api | ||
| charts | ||
| colors | ||
| components | ||
| composables | ||
| constants | ||
| dashboards | ||
| 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.