ff7b2daf7a
The Gospel x Internet dashboard needs the Driver's vertical legend on the side to select a people-group list and filter its groups by it. This is that legend, wired as a selector. It WRAPS the shared semantic tree legend rather than replacing it. That component is already the vertical legend and already drives the 26-zone tapestry, so every fix it receives -- theme-awareness, the progress bar, the mobile sheet path, scroll-to-selected -- keeps applying. A second widget would have to re-earn all of it. It emits the SELECTION, not resolved group ids, and that is ownership rather than taste. Resolving a zone to ids means joining zone membership against the group rows, and that join is not trivial: the membership keys are ASCII while the province data carries diacritics, so a naive join silently loses hundreds of groups. A legend that resolved ids would hold a second copy of that join and the copies would drift -- appearing as a wrong count, which nobody notices. The consumer already holds the rows and the join. A region row selects the union of its zones, and both a leaf and a parent return arrays, so a single zone is not a special case the consumer will eventually get wrong. A cleared selection is representable, because a dashboard must be able to drop its filter. The selection rule sits in its own module with its own check, including a negative control that a parent does not select only itself -- which would filter to nothing while looking like it had worked. The tree is a prop. Its builder lives in the plugin that owns the zoning, and a cross-plugin import is barred, so promoting that helper to the library is a separate coordinated move. |
||
|---|---|---|
| .. | ||
| charts | ||
| dashboards | ||
| hints | ||
| legends | ||
| map-controls | ||
| poster | ||
| qa | ||
| regions | ||
| search | ||
| tables | ||
| 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.