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

Skip to content

Quick fix for output() support in elements #57535

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

alxhub
Copy link
Member

@alxhub alxhub commented Aug 26, 2024

No description provided.

@alxhub alxhub added the target: major This PR is targeted for the next major release label Aug 26, 2024
@angular-robot angular-robot bot added the detected: breaking change PR contains a commit with a breaking change label Aug 26, 2024
@pullapprove pullapprove bot requested a review from AndrewKushnir August 26, 2024 21:16
@angular-robot angular-robot bot added the area: elements Issues related to Angular Elements label Aug 26, 2024
@pullapprove pullapprove bot requested a review from dylhunn August 26, 2024 21:16
@ngbot ngbot bot added this to the Backlog milestone Aug 26, 2024
Previously Elements was assuming that every output was an RxJS `Subject` and
supports `.pipe()`. This is not true for `output()`-based outputs which
have `.subscribe()` but not `.pipe()`. This commit fixes such outputs by
using a `new Observable` instead of `map` to forward outputs.
@angular-robot angular-robot bot removed the detected: breaking change PR contains a commit with a breaking change label Aug 26, 2024
@alxhub alxhub added the action: merge The PR is ready for merge by the caretaker label Sep 3, 2024
@AndrewKushnir
Copy link
Contributor

This PR was merged into the repository by commit fe5c4e0.

The changes were merged into the following branches: main

@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 Oct 4, 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: elements Issues related to Angular Elements target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants