Repository navigation
Conversation
This branch has not been deployed
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 #7649.
Public error values now use
unknownacross the RxJS Next platform and RxJS surfaces, including observer/subscriber/inspector callbacks, native and ColdObservablecatch, Subject variants,catchError, bothtapforms,retry,retryWhen, share reset callbacks, and notifications. Runtime propagation remains unchanged.This is an intentional type-only breaking change from RxJS 7. The migration and API guidance now tell consumers to narrow errors before accessing properties.
Validation:
pnpm --filter @rxjs/observable-polyfill run buildpnpm --filter rxjs run buildpnpm --filter rxjs run test:typespnpm --filter @rxjs/observable-polyfill test -- --run(52 tests)