Repository navigation
Correct when derived signal functions run - #1647
Merged
Merged
Conversation
|
|
✅ Deploy Preview for solid-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
LadyBluenotes
requested changes
Sep 30, 2026
LadyBluenotes
approved these changes
Oct 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #692
Derived signals are plain functions, so changing a dependency does not call them by itself. This updates the guide to explain that the caller's tracking scope is what reruns, adds a one-time read versus createEffect example, and clarifies component-body reads and uncached calculations versus createMemo.
Checked the MDX compiles, Prettier, and git diff --check. Runtime assertions with Solid 1.9.14 verify manual reads do not rerun when count changes, while an effect does. Full site build and rendered-page checks have not been run.