History

doxa-maps-88655c70 90ceac36ba PinHint must not require vue-i18n either, and a gate so the next one is caught The shepherd reported a P0 I caused: `db36397b` made library FilterDropdown call useI18n() unconditionally, which throws "Need to install with `app.use`" on any host that never installed vue-i18n. people-groups-grid deliberately has none, so the grid rendered blank standalone, in the studio and in every composite nesting it -- one of the seven production plugins going to DX. Studio fixed that instance in `6603dc17`. That fix was NOT on my branch. `6603dc17` was not an ancestor of my HEAD and my tree still carried the unguarded call, so my next push would have reverted it. Merged before doing anything else. PinHint carried the same unguarded call, added by me in `9ba6ad7a`. Guarded the same way: host translations when present, the English literal otherwise, with te() answering false so callers fall through to their own defaults. The gate the shepherd asked for is _chk-library-i18n-optional.mjs. It scans library/components for useI18n() calls that are not behind a guard, and it separates LIVE from LATENT, because a wall of identical failures gets ignored while a list of one gets fixed: it computes which bundles install no i18n and which of those actually import each offender. Measured: 17 library components still call useI18n() unguarded, 7 bundles install no i18n (big-picture, doxa-maps-spa, doxa-vision-card, golden-path-check, people-groups-grid, plugin-studio, stack-demo), and LIVE is currently none -- no bare host renders an unguarded component today. The 17 are debt, not safety. They are left for their owners rather than rewritten from here, since library/ reaches every bundle. Two of my own errors on the way, both caught before they reached anyone. I first reported 14 bare bundles, because I grepped for createI18n when the install is usually createAppI18n from @map/i18n -- country-posters does install it. And the gate first reported PeopleGroupDetail as LIVE in people-groups-grid on the strength of a COMMENT mentioning it: a substring match cannot tell an import from prose, which is precisely the defect I reported in check:shared-reached a day earlier and then rebuilt myself. It now strips comments and requires a real import statement or an element tag.		2026-09-25 03:43:56 +00:00
..
charts	Prepare repo to the vision: BLUF vision-cast README, library warning, SRI injection, term scrub	2026-09-15 22:58:19 +00:00
hints	PinHint must not require vue-i18n either, and a gate so the next one is caught	2026-09-25 03:43:56 +00:00
legends	legend: the height cap now derives from the offset instead of repeating it	2026-09-24 22:00:52 +00:00
map-controls	Composed maps: stop the geocoder deleting every keystroke	2026-09-24 16:16:36 +00:00
poster	poster cards: a blue outline on hover, and a gate that can see it	2026-09-24 23:17:42 +00:00
qa	Brand-neutral shared VerticalTabsLayout with lazy nested-element hosting; fix cap-5 prayer tab leaf path; neutralize library identifiers; add Forgejo CI build-gate workflow	2026-09-19 17:24:30 +00:00
search	FilterDropdown: translate when the host has i18n, never require it	2026-09-25 03:19:23 +00:00
tables	Put the tables in the house palette instead of Tabulator's stock theme	2026-09-24 03:51:06 +00:00
PeopleGroupDetail.vue	Teach the synced-CSS gate what a selector is, and turn it on	2026-09-23 01:22:36 +00:00
README.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
ResearchMapFilterPanel.vue	doxa-maps — portable bundler for embeddable JAMstack maps	2026-09-10 01:53:07 +00:00
ResearchMapSideMenu.vue	doxa-maps — portable bundler for embeddable JAMstack maps	2026-09-10 01:53:07 +00:00
SideMenuDrawer.vue	doxa-maps — portable bundler for embeddable JAMstack maps	2026-09-10 01:53:07 +00:00
ViewSelect.vue	UPG-100: lead with Prayer Resources, map second	2026-09-23 20:33:00 +00:00
WARNING.md	Complete app-profiles->plugin-designs sweep across comments/docs; build green; layouts kept at root (load-bearing)	2026-09-17 18:18:19 +00:00

README.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>, calls useShadowStyles(), and reaches stores via inject('mapStore' | 'uiStore' | 'dataStore') — never a direct store import.

Full catalog + conventions: ../../documentation/architecture/components.md · per-file roles: ../../documentation/reference.md.