d8364d949a
The previous commit did not parse, and I pushed it: check:sfc-parse exited 1 and I read the exit code after the push instead of before it. The gate names this exact cause in its own failure text — a backtick inside the shadow-CSS template literal ends the literal, so everything after it is read as code. I had written the word dark in backticks inside a CSS comment. The gate was right, it was specific, and it was already telling me. The second defect had no symptom a gate could show. The note is a direct child of .legend-sheet-root, and .legend-sheet-root>* re-enables pointer events for every direct child at the same specificity as the note's own rule and AFTER it, so that rule won. The note would have swallowed a map drag across the full width just above the sheet — the precise thing its comment claimed it must never do. Stated now after the rule that would otherwise override it. Both are the same shape: I wrote a claim in a comment and did not check the claim was true of the code beneath it. |
||
|---|---|---|
| .. | ||
| 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.