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 does not preserve i18n attribute on ng-template #52517
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
zip-fa
changed the title
control flow: migration does not preserve i18n attribute on ng-container
control flow: migration does not preserve i18n attribute on ng-tempalte
Nov 5, 2023
zip-fa
changed the title
control flow: migration does not preserve i18n attribute on ng-tempalte
control flow: migration does not preserve i18n attribute on ng-template
Nov 5, 2023
JeanMeche
added
the
core: control flow
Issues related to the built-in control flow (@if, @for, @switch)
label
Nov 5, 2023
jessicajaniuk
pushed a commit
to jessicajaniuk/angular
that referenced
this issue
Nov 7, 2023
This makes sure that i18n attributes are preserved on ng-templates being removed during the migration. fixes: angular#52517
jessicajaniuk
pushed a commit
to jessicajaniuk/angular
that referenced
this issue
Nov 7, 2023
This makes sure that i18n attributes are preserved on ng-templates being removed during the migration. fixes: angular#52517
jessicajaniuk
pushed a commit
to jessicajaniuk/angular
that referenced
this issue
Nov 7, 2023
This makes sure that i18n attributes are preserved on ng-templates being removed during the migration. fixes: angular#52517
jessicajaniuk
pushed a commit
to jessicajaniuk/angular
that referenced
this issue
Nov 7, 2023
This makes sure that i18n attributes are preserved on ng-templates being removed during the migration. fixes: angular#52517
6 tasks
jessicajaniuk
pushed a commit
to jessicajaniuk/angular
that referenced
this issue
Nov 7, 2023
This makes sure that i18n attributes are preserved on ng-templates being removed during the migration. fixes: angular#52517
jessicajaniuk
pushed a commit
to jessicajaniuk/angular
that referenced
this issue
Nov 8, 2023
This makes sure that i18n attributes are preserved on ng-templates being removed during the migration. fixes: angular#52517
atscott
pushed a commit
that referenced
this issue
Nov 8, 2023
tbondwilkinson
pushed a commit
to tbondwilkinson/angular
that referenced
this issue
Dec 6, 2023
…ngular#52597) This makes sure that i18n attributes are preserved on ng-templates being removed during the migration. fixes: angular#52517 PR Close angular#52597
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
…ngular#52597) This makes sure that i18n attributes are preserved on ng-templates being removed during the migration. fixes: angular#52517 PR Close angular#52597
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
Hi.
This code:
Got migrated to this:
I guess this is not fixable, because of strange setup with i18n attribute on ng-template. But maybe consider migrating this code to </ng-container
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?
No response
The text was updated successfully, but these errors were encountered: