-
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
Control flow schematic: ng-template + [ngIf] + let- not migrated correctly #53291
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
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
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
6 tasks
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
Thanks! fix is in #53296. |
dylhunn
pushed a commit
that referenced
this issue
Dec 5, 2023
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
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. |
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)
Which @angular/* package(s) are the source of the bug?
core
Is this a regression?
No
Description
Input:
Output:
Expected:
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
)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.The text was updated successfully, but these errors were encountered: