151fb8f0eb
The ⓘ panel now states that a dot marks where a people is found, not a town or a boundary (noteKey pins.approximate, the catalogue string the map's pin note used, in all 11 locales), so the caveat stays available to a reader who asks once the phone legend stops stating it. Also rebuilds every bundle the MapInfoButton / MapInfo change reaches, as the landing precondition names them: research-dashboard, dashboard-plus-grid, cities-internet, gospel-resources and doxa-research-map (their behaviour is unchanged: standalone is opt-in), plus doxa-simple-map for the note. Then tree + SRI.
22 lines
1.1 KiB
JavaScript
22 lines
1.1 KiB
JavaScript
// What "What can this map do?" says about Prayer Progress. The map carries it, so the ⓘ works wherever the
|
|
// map is embedded; a host (the gallery) only adds placement. The keys are the library catalogue's
|
|
// ('mapInfo' area, all 11 locales).
|
|
//
|
|
// PER PRESET. The text describes the prayer map, so it belongs to a map that shows the PRAYER tab: the
|
|
// full profile (all three tabs, prayer first) and the prayer preset. The engagement and adoption presets
|
|
// show only their own tab and have no text of their own yet, so they have no info, and no ⓘ renders
|
|
// there: no wrong copy and no untranslated text.
|
|
const PRAYER = {
|
|
storageKey: 'prayer-map',
|
|
leadKey: 'mapInfo.tab.prayer-map.lead',
|
|
takeawayKey: 'mapInfo.tab.prayer-map.takeaway',
|
|
// The approximate-location caveat, kept here where a reader who asks will find it (the map itself no
|
|
// longer states it on phones). The same catalogue string the map's pin note used.
|
|
noteKey: 'pins.approximate',
|
|
examples: [],
|
|
}
|
|
|
|
/** The map's info for the tabs it shows, or null when it has none. */
|
|
export function mapInfoFor(tabs) {
|
|
return (tabs || []).some((t) => t && t.id === 'prayer') ? PRAYER : null
|
|
}
|