4e2ea5ed2c
These numbers print. A packet is handed to a reader on paper: no hover, no tooltip, no correction, no redeploy. So the arithmetic lives in its own module and is asserted against the shipped data rather than a fixture. DOXA IS NOT A SLICE. Of its 2,107 groups, 2,082 are unreached and 1,745 are frontier, so 25 are not unreached at all and 362 are not frontier. That is one group in six. A chart drawing DOXA as a fourth band nested inside frontier misstates 17.2% of the list with a clean shape and no error of any kind, which is why steps and overlays are different props and an overlay reports whether it is a slice rather than being assumed to be one. upg100 asked for the numbers to reach the caption as text too, because a printed band nobody can hover over explains nothing. Three bugs I wrote, each caught by an assertion rather than by review: The publisher warning sat in the wrong function. I put "Joshua Project counts 16,426 where IMB counts 12,379" into the nesting error, and the test proved the claim false: 16,426 on top of 12,379 is perfectly monotonic. The two are not the same kind of count, and no comparison of magnitudes can see that, so it needed a separate check reading what the numbers are OF. An error message naming a cause its own code cannot detect sends the next reader to look for the wrong thing. A percent read as a fraction filled 3,189 cells of 5,200 instead of 32. My heuristic was "above 1 means percent", and pctEvangelical is 0.6133, which is a valid fraction and a valid percent with nothing in the value to separate them. The refusal I added catches a percent of 1 or more and provably cannot catch ours, and every share this packet prints is below 1% because the subject is unreached peoples. So the guard is not the protection, the name is: fractionFromPercent states the unit in the source line. Both halves are asserted, including the half that does not work, because a guard believed to cover more than it does is the worse failure. And the rounding flags were untested until the test used values that could reach them. 0.6133% of 5,200 is 31.9 cells; the reader sees 32 and cannot see 31.9, so the exact value goes in the caption and a share too small to fill one cell is flagged rather than drawn as one. |
||
|---|---|---|
| .. | ||
| 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.