Thanks to visit codestin.com
Credit goes to github.com

Skip to content

fix(core): avoid breaking change with apps using rxjs 6.x #58341

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

Closed
wants to merge 1 commit into from

Conversation

crisbeto
Copy link
Member

The rxResource was using firstValueFrom which isn't supported in rxjs 6.x. @angular/core currently supports rxjs 6 so we need this to be backwards compatible. This came up when trying to deploy the Material docs site which is still on rxjs 6 (see).

The `rxResource` was using `firstValueFrom` which isn't supported in rxjs 6.x. `@angular/core` currently supports rxjs 6 so we need this to be backwards compatible. This came up when trying to deploy the Material docs site which is still on rxjs 6 ([see](https://github.com/angular/components/actions/runs/11487971079/job/31973721563)).
@crisbeto crisbeto added action: review The PR is still awaiting reviews from at least one requested reviewer target: rc This PR is targeted for the next release-candidate labels Oct 24, 2024
@crisbeto crisbeto requested a review from alxhub October 24, 2024 06:33
@angular-robot angular-robot bot added the area: core Issues related to the framework runtime label Oct 24, 2024
@ngbot ngbot bot added this to the Backlog milestone Oct 24, 2024
@e-oz
Copy link

e-oz commented Oct 24, 2024

As v19 is a major release and breaking changes are allowed, it would be better to drop the RxJS v6 support.

@crisbeto
Copy link
Member Author

I generally agree about dropping rxjs 6, but from what I remember, we have kept it because the new error behavior in 7 was hugely breaking for a lot of users (internal ones included). Furthermore, since yesterday's release the breaking change window is closed.

@crisbeto crisbeto marked this pull request as ready for review October 24, 2024 06:56
.subscribe({
next: resolve,
error: reject,
complete: () => reject(new Error('Resource completed before producing a value')),
Copy link
Member Author

Choose a reason for hiding this comment

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

Note: rxjs raises an EmptyError here.

@crisbeto crisbeto added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Oct 24, 2024
@crisbeto crisbeto removed the request for review from alxhub October 24, 2024 16:21
@alxhub
Copy link
Member

alxhub commented Oct 24, 2024

This PR was merged into the repository by commit c7342be.

The changes were merged into the following branches: main, 19.0.x

@alxhub alxhub closed this in c7342be Oct 24, 2024
alxhub pushed a commit that referenced this pull request Oct 24, 2024
The `rxResource` was using `firstValueFrom` which isn't supported in rxjs 6.x. `@angular/core` currently supports rxjs 6 so we need this to be backwards compatible. This came up when trying to deploy the Material docs site which is still on rxjs 6 ([see](https://github.com/angular/components/actions/runs/11487971079/job/31973721563)).

PR Close #58341
@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 Nov 24, 2024
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 area: core Issues related to the framework runtime target: rc This PR is targeted for the next release-candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants