-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
Ivy + @Component.host + async pipe binding - Unexpected Node Error (Ivy Only) #37610
Comments
Yup, Moving from an async pipe to a static value (e.g. a simple boolean) works just fine. It'd be nice if this worked, as our specific team are heavy heavy users of RXJS, and tend to prefer that for internal behaviors and things within a component. |
Builds on top of angular#34655 to support more cases that could be using a pipe inside host bindings (e.g. ternary expressions or function calls). Fixes angular#37610.
Builds on top of angular#34655 to support more cases that could be using a pipe inside host bindings (e.g. ternary expressions or function calls). Fixes angular#37610.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
…ngular#37883) Builds on top of angular#34655 to support more cases that could be using a pipe inside host bindings (e.g. ternary expressions or function calls). Fixes angular#37610. PR Close angular#37883
🐞 bug report
Affected Package
@angular/compiler
Is this a regression?
Yes, AFAIK -- This works just fine in VE
Description
If I use a @Component.host style binding with an Async pipe, the Ivy compiler gets very very angry with me. This works just fine in VE mode.
🔬 Minimal Reproduction
https://stackblitz.com/edit/angular-ivy-n6mcgg?file=src%2Fapp%2Fhello.component.ts
🔥 Exception or Error
🌍 Your Environment
Angular Version:
Anything else relevant?
The text was updated successfully, but these errors were encountered: