Skip to content

docs(migrations): update the docs for the migration to control flow s… #61816

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

david-d-k
Copy link
Contributor

…yntax

Change the command to execute the migration, because the command stated in the previous version results in the error "Cannot find migration 'control-flow-migration' in '@angular/core'.". The new command is more in line with the docs of other migrations.

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.dev application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

Executing the command ng update @angular/core --name=control-flow-migration results in error Cannot find migration 'control-flow-migration' in '@angular/core'..

Issue Number: N/A

What is the new behavior?

The documentation is updated that shows a working command that doesn't result in an error.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

…yntax

Change the command to execute the migration, because the command stated in the previous version results in the error "Cannot find migration 'control-flow-migration' in '@angular/core'.". The new command is more in line with the docs of other migrations.
Copy link

google-cla bot commented Jun 2, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@pullapprove pullapprove bot requested a review from MarkTechson June 2, 2025 08:01
@angular-robot angular-robot bot added area: docs Related to the documentation area: migrations Issues related to `ng update` migrations labels Jun 2, 2025
@ngbot ngbot bot added this to the Backlog milestone Jun 2, 2025
@JeanMeche
Copy link
Member

We'll need to land #61773 first.

@google-cla google-cla bot added cla: yes and removed cla: no labels Jun 2, 2025
@JeanMeche JeanMeche added action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release labels Jun 4, 2025
@kirjs
Copy link
Contributor

kirjs commented Jun 4, 2025

This PR was merged into the repository by commit b9d7e7d.

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

@kirjs kirjs closed this in b9d7e7d Jun 4, 2025
kirjs pushed a commit that referenced this pull request Jun 4, 2025
…yntax (#61816)

Change the command to execute the migration, because the command stated in the previous version results in the error "Cannot find migration 'control-flow-migration' in '@angular/core'.". The new command is more in line with the docs of other migrations.

PR Close #61816
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action: merge The PR is ready for merge by the caretaker area: docs Related to the documentation area: migrations Issues related to `ng update` migrations cla: yes target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants