RxJS deprecation fixes #17649
Merged
RxJS deprecation fixes #17649
Conversation
This file contains 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
myabc
added
maintenance
dependencies
oliverguenther
approved these changes
Jan 27, 2025
oliverguenther
force-pushed
the
housekeeping/rxjs-deprecation-fixes
branch
from
e325a6a to
21c1166
Compare
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.
Ticket
N/A
What are you trying to accomplish?
I came across various RxJS deprecation warnings while working on another bug fix. This PR deals with those potential breaking changes preemptively to make upgrading easier (e.g. the deprecated
groupByfunction overload will be removed in RxJS 8).Screenshots
What approach did you choose and why?
Merge checklist