Skip to content

fix(migrations): fixes CF migration i18n ng-template offsets #53212

Closed
jessicajaniuk wants to merge 1 commit intoangular:mainfrom
jessicajaniuk:migration-i18n
Closed

fix(migrations): fixes CF migration i18n ng-template offsets #53212
jessicajaniuk wants to merge 1 commit intoangular:mainfrom
jessicajaniuk:migration-i18n

Conversation

@jessicajaniuk
Copy link
Contributor

This addresses an issue where multiple ng-templates are present with i18n attributes. The offsets would be incorrectly accounted for when being replaced with an ng-container.

fixes: #53149

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix

Does this PR introduce a breaking change?

  • Yes
  • No

@jessicajaniuk jessicajaniuk added action: review The PR is still awaiting reviews from at least one requested reviewer target: patch This PR is targeted for the next patch release area: migrations Issues related to `ng update`/`ng generate` migrations labels Nov 27, 2023
@ngbot ngbot bot added this to the Backlog milestone Nov 27, 2023
This addresses an issue where multiple ng-templates are present with i18n attributes. The offsets would be incorrectly accounted for when being replaced with an ng-container.

fixes: angular#53149
@jessicajaniuk jessicajaniuk added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Nov 28, 2023
@pkozlowski-opensource
Copy link
Member

This PR was merged into the repository by commit f1b7d40.

pkozlowski-opensource pushed a commit that referenced this pull request Nov 28, 2023
This addresses an issue where multiple ng-templates are present with i18n attributes. The offsets would be incorrectly accounted for when being replaced with an ng-container.

fixes: #53149

PR Close #53212
@jessicajaniuk jessicajaniuk deleted the migration-i18n branch November 28, 2023 17:09
@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 Dec 29, 2023
ChellappanRajan pushed a commit to ChellappanRajan/angular that referenced this pull request Jan 23, 2024
…#53212)

This addresses an issue where multiple ng-templates are present with i18n attributes. The offsets would be incorrectly accounted for when being replaced with an ng-container.

fixes: angular#53149

PR Close angular#53212
rlmestre pushed a commit to rlmestre/angular that referenced this pull request Jan 26, 2024
…#53212)

This addresses an issue where multiple ng-templates are present with i18n attributes. The offsets would be incorrectly accounted for when being replaced with an ng-container.

fixes: angular#53149

PR Close angular#53212
amilamen pushed a commit to amilamen/angular that referenced this pull request Jan 26, 2024
…#53212)

This addresses an issue where multiple ng-templates are present with i18n attributes. The offsets would be incorrectly accounted for when being replaced with an ng-container.

fixes: angular#53149

PR Close angular#53212
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: migrations Issues related to `ng update`/`ng generate` migrations target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Control flow schematic: multiple ngIf usages with the i18n attribute produces invalid code

4 participants

Comments