From 75d85bf904d538524bc088025ac8e0151c0a3f18 Mon Sep 17 00:00:00 2001 From: Scott Idem Date: Wed, 1 Apr 2026 19:39:26 -0400 Subject: [PATCH] Working through bugs... Related to data stores and not using the for type and for id... They were locked. --- src/lib/elements/element_data_store.svelte | 14 ++++++++++++++ src/routes/idaa/+layout.svelte | 3 ++- 2 files changed, 16 insertions(+), 1 deletion(-) diff --git a/src/lib/elements/element_data_store.svelte b/src/lib/elements/element_data_store.svelte index 2fd7cec4..09042658 100644 --- a/src/lib/elements/element_data_store.svelte +++ b/src/lib/elements/element_data_store.svelte @@ -147,6 +147,20 @@ $effect(() => { }); }); +// Context Change Guard: reset loading status when identity props change. +// WHY: ds_loading_status persists after the initial load cycle ('loaded', 'not found', etc.). +// When for_id/for_type/ds_code change after mount (e.g. for_id resolves from undefined +// to a real event_id), the trigger effect below won't re-fire unless we reset to 'starting'. +// untrack() prevents a circular dep — we write ds_loading_status but don't subscribe to it here. +$effect(() => { + void for_id; + void for_type; + void ds_code; + untrack(() => { + ds_loading_status = 'starting'; + }); +}); + // Initial Trigger & Context Change Guard $effect(() => { const account_id = $slct.account_id; diff --git a/src/routes/idaa/+layout.svelte b/src/routes/idaa/+layout.svelte index f0845aba..976e1ea4 100644 --- a/src/routes/idaa/+layout.svelte +++ b/src/routes/idaa/+layout.svelte @@ -353,7 +353,7 @@ $effect(() => { - Æ IDAA + Æ IDAA { {@render children?.()} +