From 9f4e4fe607b81f208b6e83274523e98e2a7f5b1e Mon Sep 17 00:00:00 2001 From: Tito Date: Sun, 26 Oct 2025 00:08:07 -0300 Subject: [PATCH] Refine signal tracking explanation in intro-to-reactivity Clarified the explanation of signal tracking and initialization. --- src/routes/concepts/intro-to-reactivity.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/routes/concepts/intro-to-reactivity.mdx b/src/routes/concepts/intro-to-reactivity.mdx index 5b885169d..7b2bfb4f5 100644 --- a/src/routes/concepts/intro-to-reactivity.mdx +++ b/src/routes/concepts/intro-to-reactivity.mdx @@ -127,9 +127,9 @@ setCount(1); // `count` is not being tracked, so the console log will not update when `count` changes. ``` -Since initialization is a **one-time event**, if a signal is accessed _outside of a tracking scope_, it will not be tracked. +Initialization, or creation is a **one-time event** that doesn't cause tracking. To track a signal, it must be accessed within the scope of a subscriber. -Reactive primitives, such as [effects](/concepts/effects), can be used to create subscribers. +Reactive primitives, such as [memos](/concepts/derived-values/memos) can be used to create derived values from signals or other memos, and [effects](/concepts/effects) to create subscribers that use the reactive graph output once it's settled. ```jsx const [count, setCount] = createSignal(0);