-
Notifications
You must be signed in to change notification settings - Fork 27.1k
Control flow migration fails for async pipe with unboxing of observable. #52756
Copy link
Copy link
Closed
Labels
area: migrationsIssues related to `ng update`/`ng generate` migrationsIssues related to `ng update`/`ng generate` migrationscore: control flowIssues related to the built-in control flow (@if, @for, @switch)Issues related to the built-in control flow (@if, @for, @switch)
Milestone
Description
Which @angular/* package(s) are the source of the bug?
core
Is this a regression?
Yes
Description
I run the control flow migration on my code and it failed compilation.
before:
<ng-container *ngIf="value$ | async; let value">
{{value}}
after:
@if (value$ | async; let value) {
{{value}}
}
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Property 'value' does not exist on type 'Page'. Did you mean 'value$'?
Please provide the environment you discovered this bug in (run ng version)
Angular CLI: 17.0.0
Node: 20.9.0
Package Manager: yarn 1.22.19
OS: win32 x64
Angular: 17.0.1
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1700.0
@angular-devkit/build-angular 17.0.0
@angular-devkit/core 17.0.0
@angular-devkit/schematics 17.0.0
@angular/cdk 17.0.0
@angular/cli 17.0.0
@schematics/angular 17.0.0
rxjs 7.8.1
typescript 5.2.2
zone.js 0.14.2
Anything else?
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area: migrationsIssues related to `ng update`/`ng generate` migrationsIssues related to `ng update`/`ng generate` migrationscore: control flowIssues related to the built-in control flow (@if, @for, @switch)Issues related to the built-in control flow (@if, @for, @switch)