Skip to content

fix(migrations): Fix cf migration bug with parsing for loop conditions properly#53558

Closed
jessicajaniuk wants to merge 1 commit intoangular:mainfrom
jessicajaniuk:long-ternary
Closed

fix(migrations): Fix cf migration bug with parsing for loop conditions properly#53558
jessicajaniuk wants to merge 1 commit intoangular:mainfrom
jessicajaniuk:long-ternary

Conversation

@jessicajaniuk
Copy link
Copy Markdown
Contributor

The order of operations for getting for loop parts was inverted resulting in the StringStack to never be reduced.

fixes: #53555

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

…s properly

The order of operations for getting for loop parts was inverted resulting in the StringStack to never be reduced.

fixes: angular#53555
@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 Dec 13, 2023
@ngbot ngbot bot modified the milestone: Backlog Dec 13, 2023
@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 Dec 13, 2023
@atscott
Copy link
Copy Markdown
Contributor

atscott commented Dec 14, 2023

This PR was merged into the repository by commit db6b4a6.

@atscott atscott closed this in db6b4a6 Dec 14, 2023
atscott pushed a commit that referenced this pull request Dec 14, 2023
…s properly (#53558)

The order of operations for getting for loop parts was inverted resulting in the StringStack to never be reduced.

fixes: #53555

PR Close #53558
@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 Jan 14, 2024
ChellappanRajan pushed a commit to ChellappanRajan/angular that referenced this pull request Jan 23, 2024
…s properly (angular#53558)

The order of operations for getting for loop parts was inverted resulting in the StringStack to never be reduced.

fixes: angular#53555

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

The order of operations for getting for loop parts was inverted resulting in the StringStack to never be reduced.

fixes: angular#53555

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

The order of operations for getting for loop parts was inverted resulting in the StringStack to never be reduced.

fixes: angular#53555

PR Close angular#53558
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: ngFor with large nested ternary produces invalid code

4 participants