Tell users what migrations were actually performed instead of what was considered

[StephenFluin]

Command

update

Description

Currently ng update does a good job of telling you which migrations the CLI is attempting to apply, but you don't know which migrations actually were applied.

Describe the solution you'd like

I'd love it if the migrations reports / logs actually logged what changes were made. Example console output before:

UPDATE angular.json (3617 bytes)
  Migration completed.

▸ Remove 'showCircularDependencies' option from browser and server builders.
  Migration completed.

▸ Replace 'defaultCollection' option in workspace configuration with 'schematicCollections'.
  Migration completed.

▸ Update Angular packages 'dependencies' and 'devDependencies' version prefix to '^' instead of '~'.

Example after:

UPDATE angular.json (3617 bytes)
  Migration completed - no changes made.

▸ Remove 'showCircularDependencies' option from browser and server builders.
  Migration completed - no changes made.

▸ Replace 'defaultCollection' option in workspace configuration with 'schematicCollections'.
  Migration completed - 3 updates made.

▸ Update Angular packages 'dependencies' and 'devDependencies' version prefix to '^' instead of '~'.
Migration completed - 15 updates made.

Describe alternatives you've considered

No response

[angular-robot]

This feature request is now candidate for our backlog! In the next phase, the community has 60 days to upvote. If the request receives more than 20 upvotes, we'll move it to our consideration list.

You can find more details about the feature request process in our documentation.

[StephenFluin]

❤️

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