fix(@angular/cli): remove the need to specify --migrate-only when --name is used during ng update

[alan-agius4]

This commit updates the behaviour of ng update --migrate-only to remove the need for --migrate-only option to be specified. --migrate-only will be set internally.

Before

ng update @angular/cli --migrate-only --name=migration-name

Now

ng update @angular/cli --name=migration-name

[alan-agius4]

As discussed offline @dgp1130.

[dgp1130]

Typo in commit message, I think you meant:

This commit updates the behaviour of ng update --name=some-migration to remove the need for --migrate-only option to be specified. --migrate-only will not be set internally.

Also shouldn't be be "--migration-only will be set internally"? Or am I misunderstanding the message?

[alan-agius4]

Typo in commit message, I think you meant:

This commit updates the behaviour of ng update --name=some-migration to remove the need for --migrate-only option to be specified. --migrate-only will not be set internally.

Also shouldn't be be "--migration-only will be set internally"? Or am I misunderstanding the message?

Yes you are right

[angular-automatic-lock-bot]

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.}