Skip to content

Control flow migration fixes#59861

Closed
crisbeto wants to merge 2 commits intoangular:mainfrom
crisbeto:59846/control-flow-dep-detection
Closed

Control flow migration fixes#59861
crisbeto wants to merge 2 commits intoangular:mainfrom
crisbeto:59846/control-flow-dep-detection

Conversation

@crisbeto
Copy link
Copy Markdown
Member

@crisbeto crisbeto commented Feb 5, 2025

Fixes a couple of issues with the control flow migration:

fix(migrations): count used dependencies inside existing control flow

Fixes that the control flow migration wasn't checking the content of pre-existing control flow nodes for dependencies.

fix(migrations): account for let declarations in control flow migration

Fixes that the control flow migration wasn't accounting for @let when determining which symbols are used.

Fixes #59846.

Fixes that the control flow migration wasn't checking the content of pre-existing control flow nodes for dependencies.

Fixes angular#59846.
Fixes that the control flow migration wasn't accounting for `@let` when determining which symbols are used.
@crisbeto crisbeto 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 labels Feb 5, 2025
@angular-robot angular-robot bot added the area: migrations Issues related to `ng update`/`ng generate` migrations label Feb 5, 2025
@ngbot ngbot bot added this to the Backlog milestone Feb 5, 2025
Copy link
Copy Markdown
Contributor

@thePunderWoman thePunderWoman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And here I thought we'd @let it go. Nice work, @crisbeto.

@thePunderWoman thePunderWoman 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 Feb 5, 2025
@crisbeto
Copy link
Copy Markdown
Member Author

crisbeto commented Feb 5, 2025

You should be able to update to the new version, run the command and then roll back the update.

@atscott
Copy link
Copy Markdown
Contributor

atscott commented Feb 12, 2025

This PR was merged into the repository by commit aa285c5.

The changes were merged into the following branches: main, 19.1.x

@atscott atscott closed this in 1119f85 Feb 12, 2025
atscott pushed a commit that referenced this pull request Feb 12, 2025
…on (#59861)

Fixes that the control flow migration wasn't accounting for `@let` when determining which symbols are used.

PR Close #59861
atscott pushed a commit that referenced this pull request Feb 12, 2025
…#59861)

Fixes that the control flow migration wasn't checking the content of pre-existing control flow nodes for dependencies.

Fixes #59846.

PR Close #59861
atscott pushed a commit that referenced this pull request Feb 12, 2025
…on (#59861)

Fixes that the control flow migration wasn't accounting for `@let` when determining which symbols are used.

PR Close #59861
@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 Mar 15, 2025
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.

Migration to Control Flow Syntax Removes CommonModule While Still Needed

3 participants