68c51dbc2a
Two phone legend fixes in LegendMobile. The rule that moves the engine's bottom corners to the top lives in CSS injected once into the host's shadow root and never removed. Cities with Internet mounts the sheet only for its phone people-group card, so after "back to legend" its credit stayed at the top, under the map's own legend (measured at 390: 1 of 11 points visible). The move is now scoped to a class on the host that is set while at least one LegendMobile is mounted, counted so the desktop legend's hidden twin cannot clear it early. A drag on the sheet's handle fell through to whatever scrolls behind the map: on UPG-100's Map view a downward drag on the collapsed sheet scrolled its pane column 655px back to the list. The handle (the drag strip, the title rows, and the whole sheet while collapsed) now has touch-action:none, and a collapsed sheet holds the gesture as a backstop. A tap still reaches the caret. |
||
|---|---|---|
| .. | ||
| 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.