Skip to content
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

Removed deprecated symbols that have a new name #7164

Merged
merged 10 commits into from
Jan 24, 2023

Conversation

demensky
Copy link
Contributor

Exported symbols marked as "Renamed to $SYMBOL_NAME. Will be removed in v8" have been removed. The entire project was also searched and all references to deleted entities were updated.

BREAKING CHANGE: removed deprecated symbols that have a new name

Related issue (if exists): #6367

BREAKING CHANGE: The `animationFrame` constant is no longer available. Use `animationFrameScheduler`.
BREAKING CHANGE: The `ObservableLike` interface is no longer available. Use `InteropObservable`.
BREAKING CHANGE: The `ObservedValuesFromArray` interface is no longer available. Use `ObservedValueUnionFromArray`.
BREAKING CHANGE: The `combineAll` operator is no longer available. Use `combineLatestAll`.
BREAKING CHANGE: The `flatMap` operator is no longer available. Use `mergeMap`.
BREAKING CHANGE: The `exhaust` operator is no longer available. Use `exhaustAll`.
BREAKING CHANGE: The `asap` constant is no longer available. Use `asapScheduler`.
BREAKING CHANGE: The `queue` constant is no longer available. Use `queueScheduler`.
BREAKING CHANGE: The `async` constant is no longer available. Use `asyncScheduler`.
@demensky demensky changed the title Remove rename Removed deprecated symbols that have a new name Jan 21, 2023
@demensky
Copy link
Contributor Author

I can’t figure out why “CI / Node 14 build” is crashing. I installed the same version of node locally but the tests pass.

@benlesh, maybe this is some kind of anomaly?

example

@benlesh
Copy link
Member

benlesh commented Jan 24, 2023

Not sure... It might have something to do with the transpiled output using a feature that doesn't exist in Node 14, and being somehow different than what is happening locally. Different TS version locally maybe?

BREAKING CHANGE: The `onErrorResumeNext` operator is no longer available. Use `onErrorResumeNextWith`.
@demensky
Copy link
Contributor Author

@benlesh I restarted and it's gone. It looks like it's some kind of floating bug in old node or tests in the repository.

@benlesh benlesh merged commit de7becf into ReactiveX:master Jan 24, 2023
@benlesh
Copy link
Member

benlesh commented Jan 24, 2023

Thank you, @demensky

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants