Skip to content

fix(migrations): Fix empty switch case offset bug in cf migration#53839

Closed
jessicajaniuk wants to merge 1 commit intoangular:mainfrom
jessicajaniuk:switch-template
Closed

fix(migrations): Fix empty switch case offset bug in cf migration#53839
jessicajaniuk wants to merge 1 commit intoangular:mainfrom
jessicajaniuk:switch-template

Conversation

@jessicajaniuk
Copy link
Copy Markdown
Contributor

This addresses the offset issue caused when a switch case was empty with no spaces or children being affected by the markers that were added, but not accounted for in offset. The markers are not needed for empty content and can be safely removed in this case. This addresses the issue reported by @yharaskrik.

fixes: #53779

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

This addresses the offset issue caused when a switch case was empty with no spaces or children being affected by the markers that were added, but not accounted for in offset. The markers are not needed for empty content and can be safely removed in this case.

fixes: angular#53779
@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 Jan 8, 2024
@jessicajaniuk jessicajaniuk requested a review from crisbeto January 8, 2024 19:05
@ngbot ngbot bot added this to the Backlog milestone Jan 8, 2024
@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 Jan 9, 2024
@atscott
Copy link
Copy Markdown
Contributor

atscott commented Jan 9, 2024

This PR was merged into the repository by commit d0b95d5.

atscott pushed a commit that referenced this pull request Jan 9, 2024
…3839)

This addresses the offset issue caused when a switch case was empty with no spaces or children being affected by the markers that were added, but not accounted for in offset. The markers are not needed for empty content and can be safely removed in this case.

fixes: #53779

PR Close #53839
@atscott atscott closed this in d0b95d5 Jan 9, 2024
ChellappanRajan pushed a commit to ChellappanRajan/angular that referenced this pull request Jan 23, 2024
…gular#53839)

This addresses the offset issue caused when a switch case was empty with no spaces or children being affected by the markers that were added, but not accounted for in offset. The markers are not needed for empty content and can be safely removed in this case.

fixes: angular#53779

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

This addresses the offset issue caused when a switch case was empty with no spaces or children being affected by the markers that were added, but not accounted for in offset. The markers are not needed for empty content and can be safely removed in this case.

fixes: angular#53779

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

This addresses the offset issue caused when a switch case was empty with no spaces or children being affected by the markers that were added, but not accounted for in offset. The markers are not needed for empty content and can be safely removed in this case.

fixes: angular#53779

PR Close angular#53839
@angular-automatic-lock-bot
Copy link
Copy Markdown

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 Feb 9, 2024
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 Migration does not work correctly on template

4 participants