From 8b78e5486d7457facbef4ac964a1fb8a6f1f6d7d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marc-Andr=C3=A9=20Bombeck?= Date: Sat, 26 Sep 2026 10:05:55 +0200 Subject: [PATCH] docs(daily): note that a new rail kind needs its stored lists extended The start-page item choice stores the enabled kinds, so a list saved before a kind existed reads as that kind switched off. Say so next to the kind list, where the next kind will be added. --- src/lib/daily/priority-item.ts | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/lib/daily/priority-item.ts b/src/lib/daily/priority-item.ts index 6fc3b6c76..fda13e6f5 100644 --- a/src/lib/daily/priority-item.ts +++ b/src/lib/daily/priority-item.ts @@ -25,6 +25,13 @@ import type { ModuleKey } from "@/lib/modules/registry"; * dashboard-layout label. Typed consumers derive from this tuple so stored * visibility settings and API validation cannot accept vocabulary the current * build does not understand. + * + * A new kind also needs a data migration that appends it to every stored, + * non-empty `enabledHeroItemKinds` list. The layout stores the ENABLED kinds + * whenever they are not all of them, so a list saved before the kind existed + * reads as "switched off" and the new kind never shows for that person. + * `upcoming_visit` shipped without one and stayed hidden that way until + * migration 0355 appended it. */ export const PRIORITY_ITEM_KINDS = [ "coach_checkin",