doxa-life/doxa-maps
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Register the two wave-3c sites, with the third column their code actually has

Browse source 
The rows studio removed when 4c05e589 was not in their landing go back in — but NOT as
regions-plugin wrote them. 4c05e589 had the third column as humanizeKey(k), which was correct for
the migration it was written against and became wrong the moment dx-shepherd took the product call
(UPGHK) to DELETE that fallback. A register row asserting a fallback the code no longer passes fails
by design, which is the same hole regions flagged to me in the opposite direction.

So both sites register with null: no fallback, resolve through the catalogue. The gate then asserts
!/fallback:/ rather than a fragment, which is exactly what the code now does.
This commit is contained in:
Doxa Maps 2026-09-27 01:37:45 +00:00
parent b97897b7bd
commit 1f186070a5
1 changed files with 15 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
internal/check-optional-t-equivalence.mjs
View file

@ -138,6 +138,21 @@ const SITES = [
['plugin-designs/cities-internet/connectivity-list.vue', 'useOptionalT', null],
['plugin-designs/cities-internet/connectivity-map.vue', 'useOptionalT', null],
['plugin-designs/cities-internet/data-tables.vue', 'useOptionalT', null],
// wave 3c — my-upg-100-list (owner: upg100-plugin). NOTE THE THIRD COLUMN: these two arrive with NO
// fallback, not with humanizeKey(k). regions-plugin's 4c05e589 had them as 'humanizeKey(k)' — correct
// for the migration it was written against, and wrong the moment the fallback was DELETED.
// ★ WHY THEY MOVED TO THE CATALOGUE. humanizeKey rendered a key's last segment title-cased, which
// failed two different ways: on the messages keys it printed "Upg100 Wall Intro" where a whole
// sentence exists (wrong even in English), and on the tabs keys it printed the RIGHT English by
// coincidence — the key is named after the word — so it looked correct forever while every
// non-English reader silently got English. A fallback that agrees with en is indistinguishable from
// a working translation until someone changes locale.
// The premise for keeping it ("these keys are not fully catalogued") was mine and was FALSE: seven
// keys across both files, all string literals, every one present in all eleven locales, 0 gaps.
// Product call taken by dx-shepherd (UPGHK, 2026-09-27) because it changes what seven vue-i18n-less
// bundles render — the same class of decision gospel-plugin took for its four sites above.
['plugin-designs/my-upg-100-list/poster-wall.vue', 'useOptionalT', null],
['plugin-designs/my-upg-100-list/upg-100-mfe.vue', 'useOptionalT', null],
]
// ★ ONE FILE KEEPS TWO BARE useI18n CALLS ON PURPOSE, and the count is asserted rather than waived.
// resources-map.vue reads the LOCALE twice (`useI18n().locale.value`) to decide isEnglish and the