docs(signals): clarify when to use linkedSignal vs computed#67324
Open
anushkasingh-commits wants to merge 5 commits intoangular:mainfrom
Open
docs(signals): clarify when to use linkedSignal vs computed#67324anushkasingh-commits wants to merge 5 commits intoangular:mainfrom
anushkasingh-commits wants to merge 5 commits intoangular:mainfrom
Conversation
Improved wording to clarify how beginners can verify their environment and IDE are correctly set up after running the app.
Contributor
|
Could you please rebase so it can be a single commit? |
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
3 participants
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.
What does this PR do?
Adds a short clarifying paragraph explaining when
linkedSignalshould be preferred overcomputed.The existing documentation explains how
linkedSignalworks, but readers may still be unsure about the conceptual difference between derivation (computed) and writable derived state (linkedSignal).This PR introduces a small inline paragraph to clarify that
linkedSignalis useful when derived state must remain writable or preserve user-driven updates while still reacting to a source signal.Why is this change needed?
While reading the guide, it was not immediately clear when to choose
linkedSignalinstead ofcomputed.This clarification aims to reduce that confusion for future readers without restructuring the existing documentation.
Scope