docs: add RxJS patterns to signals migration documentation#68764
Open
aanchalsh wants to merge 1 commit into
Open
docs: add RxJS patterns to signals migration documentation#68764aanchalsh wants to merge 1 commit into
aanchalsh wants to merge 1 commit into
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The current RxJS interop documentation explains the core APIs (
toSignal,toObservable, andrxResource) but does not provide practical migration guidance for developers transitioning from common RxJS patterns to Angular signals.Issue Number: N/A
What is the new behavior?
This PR adds a migration guide for common RxJS patterns and their signal-based equivalents.
The documentation includes practical examples for:
BehaviorSubject→signalcombineLatest→computedswitchMap→resourcedistinctUntilChanged→ signal equalitydebounceTime→toObservabletakeUntilDestroyed→ automatic cleanupAdditional improvements include:
{avoid}and{prefer}migration examplesDoes this PR introduce a breaking change?
Other information
This PR focuses on improving the migration experience for developers adopting Angular signals in existing RxJS-heavy applications.