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 migration doesnt migrate code with *ngIf else directive #52502
Labels
Milestone
Comments
crisbeto
added
state: has PR
area: migrations
Issues related to `ng update` migrations
bug
labels
Nov 3, 2023
crisbeto
added a commit
to crisbeto/angular
that referenced
this issue
Nov 3, 2023
Fixes that the control flow migration wasn't migrating an `*ngIf` with an `else` condition that doesn't have spaces before the `else`. Fixes angular#52502.
It's because there's no space after the |
atscott
pushed a commit
that referenced
this issue
Nov 3, 2023
Abseil-byte
pushed a commit
to Abseil-byte/angular
that referenced
this issue
Nov 5, 2023
…lar#52504) Fixes that the control flow migration wasn't migrating an `*ngIf` with an `else` condition that doesn't have spaces before the `else`. Fixes angular#52502. PR Close angular#52504
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. |
tbondwilkinson
pushed a commit
to tbondwilkinson/angular
that referenced
this issue
Dec 6, 2023
…lar#52504) Fixes that the control flow migration wasn't migrating an `*ngIf` with an `else` condition that doesn't have spaces before the `else`. Fixes angular#52502. PR Close angular#52504
ChellappanRajan
pushed a commit
to ChellappanRajan/angular
that referenced
this issue
Jan 23, 2024
…lar#52504) Fixes that the control flow migration wasn't migrating an `*ngIf` with an `else` condition that doesn't have spaces before the `else`. Fixes angular#52502. PR Close angular#52504
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Which @angular/* package(s) are the source of the bug?
core
Is this a regression?
Yes
Description
I recently tried control flow migration schematics for my project using command
ng generate @angular/core:control-flow
although this time the command didnt throw any error but it didnt work either.For eample for below teamplate:
Below is the code that this migration produced:
Please provide a link to a minimal reproduction of the bug
For this I can add you to a private repo
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response
The text was updated successfully, but these errors were encountered: