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

Control flow schematic: ng-template + [ngIf] + let- not migrated correctly #53291

Closed
mattlewis92 opened this issue Nov 30, 2023 · 2 comments
Closed
Assignees
Labels
area: migrations Issues related to `ng update` migrations core: control flow Issues related to the built-in control flow (@if, @for, @switch)
Milestone

Comments

@mattlewis92
Copy link
Contributor

Which @angular/* package(s) are the source of the bug?

core

Is this a regression?

No

Description

Input:

<ng-template [ngIf]="viewModel$ | async" let-vm>
  {{vm | json}}
</ng-template>

Output:

@if (viewModel$ | async) {
  {{vm | json}}
}

Expected:

@if (viewModel$ | async; as vm) {
  {{vm | json}}
}

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

No response

Please provide the environment you discovered this bug in (run ng version)

Angular CLI: 17.0.5
Node: 18.17.1
Package Manager: pnpm 8.11.0
OS: darwin arm64

Angular: 17.1.0-next.2+sha-1940280
... core

Package                             Version
-------------------------------------------------------------
@angular-devkit/architect           0.1700.1
@angular-devkit/build-angular       17.0.5
@angular-devkit/core                17.0.5
@angular-devkit/schematics          17.0.5
@angular/animations                 17.0.5
@angular/cdk                        17.0.1
@angular/cli                        17.0.5
@angular/common                     17.0.5
@angular/compiler                   17.0.5
@angular/compiler-cli               17.0.5
@angular/elements                   17.0.5
@angular/forms                      17.0.5
@angular/google-maps                15.2.9
@angular/language-service           17.0.5
@angular/localize                   17.0.5
@angular/platform-browser           17.0.5
@angular/platform-browser-dynamic   17.0.5
@angular/router                     17.0.5
@angular/service-worker             17.0.5
@schematics/angular                 17.0.5
ng-packagr                          17.0.2
rxjs                                7.8.0
typescript                          5.2.2
webpack                             5.88.2
zone.js                             0.14.2

Anything else?

I am using "@angular/core": "angular/core-builds#17.1.0-next.2+1940280", which is built from the HEAD of the main branch and contains all the latest control flow migration fixes.

@jessicajaniuk jessicajaniuk self-assigned this Nov 30, 2023
@jessicajaniuk jessicajaniuk added area: migrations Issues related to `ng update` migrations core: control flow Issues related to the built-in control flow (@if, @for, @switch) labels Nov 30, 2023
@ngbot ngbot bot added this to the needsTriage milestone Nov 30, 2023
jessicajaniuk pushed a commit to jessicajaniuk/angular that referenced this issue Nov 30, 2023
Empty aliases are considered the item in an ngFor, and ngIf was skipping that value.

fixes: angular#53291
jessicajaniuk pushed a commit to jessicajaniuk/angular that referenced this issue Nov 30, 2023
Empty aliases are considered the item in an ngFor, and ngIf was skipping that value.

fixes: angular#53291
@jessicajaniuk
Copy link
Contributor

Thanks! fix is in #53296.

@dylhunn dylhunn closed this as completed in 6f75471 Dec 5, 2023
dylhunn pushed a commit that referenced this issue Dec 5, 2023
Empty aliases are considered the item in an ngFor, and ngIf was skipping that value.

fixes: #53291

PR Close #53296
tbondwilkinson pushed a commit to tbondwilkinson/angular that referenced this issue Dec 6, 2023
…lar#53296)

Empty aliases are considered the item in an ngFor, and ngIf was skipping that value.

fixes: angular#53291

PR Close angular#53296
@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 Jan 5, 2024
ChellappanRajan pushed a commit to ChellappanRajan/angular that referenced this issue Jan 23, 2024
…lar#53296)

Empty aliases are considered the item in an ngFor, and ngIf was skipping that value.

fixes: angular#53291

PR Close angular#53296
rlmestre pushed a commit to rlmestre/angular that referenced this issue Jan 26, 2024
…lar#53296)

Empty aliases are considered the item in an ngFor, and ngIf was skipping that value.

fixes: angular#53291

PR Close angular#53296
amilamen pushed a commit to amilamen/angular that referenced this issue Jan 26, 2024
…lar#53296)

Empty aliases are considered the item in an ngFor, and ngIf was skipping that value.

fixes: angular#53291

PR Close angular#53296
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: migrations Issues related to `ng update` migrations core: control flow Issues related to the built-in control flow (@if, @for, @switch)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants