Skip to content

refactor: use recommended approach for asserting observables #18053

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

Merged
merged 1 commit into from
Jan 22, 2020

Conversation

crisbeto
Copy link
Member

Switches the assertions for whether a value is an observable to use isObservable, rather than value instanceof Observable which has been the recommended approach since rxjs 6.1.

See ReactiveX/rxjs@edb33e5.

@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release labels Dec 27, 2019
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Dec 27, 2019
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Jan 10, 2020
Switches the assertions for whether a value is an observable to use `isObservable`, rather than `value instanceof Observable` which has been the recommended approach since rxjs 6.1.

See ReactiveX/rxjs@edb33e5.
@crisbeto crisbeto force-pushed the observable-assertions branch from 84d698c to ecb6043 Compare January 22, 2020 22:15
@jelbourn jelbourn merged commit 3e7982a into angular:master Jan 22, 2020
yifange pushed a commit to yifange/components that referenced this pull request Jan 30, 2020
…#18053)

Switches the assertions for whether a value is an observable to use `isObservable`, rather than `value instanceof Observable` which has been the recommended approach since rxjs 6.1.

See ReactiveX/rxjs@edb33e5.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Feb 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants