6b29e146df
Some checks are pending
build-gate / build (push) Waiting to run
Cluster and People Group changed the dashboard correctly and could never move the grid, because the fields behind them were not in the grid's fetch. They are real fields, unlike the two family axes, which are derived and have no row field to filter against at all — those stay unmapped rather than being aimed at a lookalike and quietly showing the wrong rows. Verified against the live data before mapping, since a wrong mapping is worse than no mapping: both fields are present on 2,106 of 2,107 rows in the same value-and-label shape as the axes already wired, with 194 and 1,736 distinct values, no collisions once normalised, and no case where one entry's label matches another's code. Codes and names never overlap, so either vocabulary can be accepted safely. Measured end to end: selecting the Telugu cluster narrows the grid to 93, which is exactly the number of rows the API holds for it. |
||
|---|---|---|
| .. | ||
| src | ||
| index.html | ||
| index.js | ||
| people-groups-grid.instances.json | ||
| people-groups-grid.meta.json | ||
| people-groups-grid.vue | ||