-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: finalize behaves well with useDeprecatedSynchronousErrorHandling #6251
Changes from all commits
0f3f53a
729ea95
d0fca8d
dcb9543
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -215,43 +215,67 @@ export class Observable<T> implements Subscribable<T> { | |
): Subscription { | ||
const subscriber = isSubscriber(observerOrNext) ? observerOrNext : new SafeSubscriber(observerOrNext, error, complete); | ||
|
||
// If we have an operator, it's the result of a lift, and we let the lift | ||
// mechanism do the subscription for us in the operator call. Otherwise, | ||
// if we have a source, it's a trusted observable we own, and we can call | ||
// the `_subscribe` without wrapping it in a try/catch. If we are supposed to | ||
// use the deprecated sync error handling, then we don't need the try/catch either | ||
// otherwise, it may be from a user-made observable instance, and we want to | ||
// wrap it in a try/catch so we can handle errors appropriately. | ||
const { operator, source } = this; | ||
|
||
let dest: any = subscriber; | ||
if (config.useDeprecatedSynchronousErrorHandling) { | ||
dest._syncErrorHack_isSubscribing = true; | ||
this._deprecatedSyncErrorSubscribe(subscriber); | ||
} else { | ||
const { operator, source } = this; | ||
subscriber.add( | ||
operator | ||
? // We're dealing with a subscription in the | ||
// operator chain to one of our lifted operators. | ||
operator.call(subscriber, source) | ||
: source | ||
? // If `source` has a value, but `operator` does not, something that | ||
// had intimate knowledge of our API, like our `Subject`, must have | ||
// set it. We're going to just call `_subscribe` directly. | ||
this._subscribe(subscriber) | ||
: // In all other cases, we're likely wrapping a user-provided initializer | ||
// function, so we need to catch errors and handle them appropriately. | ||
this._trySubscribe(subscriber) | ||
); | ||
} | ||
return subscriber; | ||
} | ||
|
||
subscriber.add( | ||
operator | ||
? operator.call(subscriber, source) | ||
: source || config.useDeprecatedSynchronousErrorHandling | ||
? this._subscribe(subscriber) | ||
: this._trySubscribe(subscriber) | ||
); | ||
/** | ||
* REMOVE THIS ENTIRE METHOD IN VERSION 8. | ||
*/ | ||
private _deprecatedSyncErrorSubscribe(subscriber: Subscriber<unknown>) { | ||
let dest: any = subscriber; | ||
dest._syncErrorHack_isSubscribing = true; | ||
const { operator } = this; | ||
if (operator) { | ||
// We don't need to try/catch on operators, as they | ||
// are doing their own try/catching, and will | ||
// properly decorate the subscriber with `__syncError`. | ||
subscriber.add(operator.call(subscriber, this.source)); | ||
} else { | ||
try { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. the primary "fix" is here for the cases where teardown wasn't being called after it was registered if a sync error was thrown. |
||
this._subscribe(subscriber); | ||
} catch (err) { | ||
dest.__syncError = err; | ||
} | ||
} | ||
|
||
if (config.useDeprecatedSynchronousErrorHandling) { | ||
dest._syncErrorHack_isSubscribing = false; | ||
// In the case of the deprecated sync error handling, | ||
// we need to crawl forward through our subscriber chain and | ||
// look to see if there's any synchronously thrown errors. | ||
// Does this suck for perf? Yes. So stop using the deprecated sync | ||
// error handling already. We're removing this in v8. | ||
while (dest) { | ||
if (dest.__syncError) { | ||
// In the case of the deprecated sync error handling, | ||
// we need to crawl forward through our subscriber chain and | ||
// look to see if there's any synchronously thrown errors. | ||
// Does this suck for perf? Yes. So stop using the deprecated sync | ||
// error handling already. We're removing this in v8. | ||
while (dest) { | ||
// Technically, someone could throw something falsy, like 0, or "", | ||
// so we need to check to see if anything was thrown, and we know | ||
// that by the mere existence of `__syncError`. | ||
if ('__syncError' in dest) { | ||
try { | ||
throw dest.__syncError; | ||
} finally { | ||
subscriber.unsubscribe(); | ||
} | ||
dest = dest.destination; | ||
} | ||
dest = dest.destination; | ||
} | ||
return subscriber; | ||
dest._syncErrorHack_isSubscribing = false; | ||
} | ||
|
||
/** @internal */ | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -58,7 +58,12 @@ import { operate } from '../util/lift'; | |
*/ | ||
export function finalize<T>(callback: () => void): MonoTypeOperatorFunction<T> { | ||
return operate((source, subscriber) => { | ||
source.subscribe(subscriber); | ||
subscriber.add(callback); | ||
// TODO: This try/finally was only added for `useDeprecatedSynchronousErrorHandling`. | ||
// REMOVE THIS WHEN THAT HOT GARBAGE IS REMOVED IN V8. | ||
try { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The "fix" for the finalize issue in the sync case is here. Note that adding a callback to a |
||
source.subscribe(subscriber); | ||
} finally { | ||
subscriber.add(callback); | ||
} | ||
}); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I split this up, and added comments. Just for organizational reasons more than anything.