mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-10-20 14:06:27 +00:00
Maurice
50f0641ad9
The keys come from the server's registry, the copy from the bundle in the browser, and a deploy parts the two for as long as it takes the page to reload: the service worker keeps serving the old app while /api/config already reports the new version, and the release notice for that very version arrives naming keys the old bundle never had. What is drawn is then system_notice.release_notes.headline where the headline belongs, on the one notice whose whole job is to be read once per release. Worse, a dismissal in that window is a real one. The entry is per-version, so whoever closes the gibberish never sees the notes for that release at all. So a notice made only of unresolved keys is held back until the reload App.tsx is already waiting for. Nothing is spent by waiting: a notice is used up by POST /dismiss and by nothing else. A release notice is judged by the strings its own two-column layout draws, not by the generic title and body it never shows. Copy written out in words rather than keyed is left alone, and one resolved string is enough to show a notice: a notice hidden by mistake is the worse failure.