Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Comments

Close side panel

fix(migrations): Fixes the root level template offset in control flow migration#52355

Closed
jessicajaniuk wants to merge 1 commit intoangular:mainangular/angular:mainfrom
jessicajaniuk:migration-templatesjessicajaniuk/angular:migration-templatesCopy head branch name to clipboard
Closed

fix(migrations): Fixes the root level template offset in control flow migration#52355
jessicajaniuk wants to merge 1 commit intoangular:mainangular/angular:mainfrom
jessicajaniuk:migration-templatesjessicajaniuk/angular:migration-templatesCopy head branch name to clipboard

Conversation

@jessicajaniuk
Copy link
Contributor

When migrating an ng-template later on in a file, the migrationResult was not being reset to zero and causing offsets to be double applied due to ng-template nodes being included in the migration loop.

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 area: migrations Issues related to `ng update`/`ng generate` migrations target: rc This PR is targeted for the next release-candidate labels Oct 24, 2023
@ngbot ngbot bot modified the milestone: Backlog Oct 24, 2023
@pullapprove pullapprove bot requested a review from dylhunn October 24, 2023 18:23
… migration

When migrating an ng-template later on in a file, the migrationResult was not being reset to zero and causing offsets to be double applied due to ng-template nodes being included in the migration loop.
@jessicajaniuk jessicajaniuk requested review from AndrewKushnir and removed request for dylhunn October 24, 2023 20:17
@pullapprove pullapprove bot requested a review from dylhunn October 24, 2023 20:18
@AndrewKushnir AndrewKushnir removed the action: review The PR is still awaiting reviews from at least one requested reviewer label Oct 24, 2023
@jessicajaniuk jessicajaniuk removed the request for review from dylhunn October 24, 2023 20:20
@jessicajaniuk jessicajaniuk added the action: merge The PR is ready for merge by the caretaker label Oct 24, 2023
@pullapprove pullapprove bot requested a review from dylhunn October 24, 2023 20:20
@jessicajaniuk jessicajaniuk removed the request for review from dylhunn October 24, 2023 21:09
@dylhunn
Copy link
Contributor

dylhunn commented Oct 24, 2023

This PR was merged into the repository by commit 90eb879.

@dylhunn dylhunn closed this in 90eb879 Oct 24, 2023
dylhunn pushed a commit that referenced this pull request Oct 24, 2023
… migration (#52355)

When migrating an ng-template later on in a file, the migrationResult was not being reset to zero and causing offsets to be double applied due to ng-template nodes being included in the migration loop.

PR Close #52355
@jessicajaniuk jessicajaniuk deleted the migration-templates branch November 9, 2023 20:34
@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 10, 2023
ChellappanRajan pushed a commit to ChellappanRajan/angular that referenced this pull request Jan 23, 2024
… migration (angular#52355)

When migrating an ng-template later on in a file, the migrationResult was not being reset to zero and causing offsets to be double applied due to ng-template nodes being included in the migration loop.

PR Close angular#52355
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: rc This PR is targeted for the next release-candidate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.