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
refactor(core): undecorated-classes-with-decorated-fields migration commits empty updates #32391
Conversation
…ommits empty updates Commit 904a201 introduced a new migration for undecorated classes with decorated Angular class members. Currently the migration always calls `tree.beginUpdate` and `tree.commitUpdate` (even if there are no changes). This causes unnecessary updates to be reported to developers running `ng update`. Once an update is commited, the CLI will report the update regardless of whether any changes were made or not. This behavior can be observed in the `ng_update_migrations` integration test. See: https://circleci.com/gh/angular/angular/438470#tests/containers/3. Notice how all source files are denoted as `UPDATED` (even though there are no changes).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
merge-assistance: SauceLabs error from master being red earlier |
…ommits empty updates (angular#32391) Commit 904a201 introduced a new migration for undecorated classes with decorated Angular class members. Currently the migration always calls `tree.beginUpdate` and `tree.commitUpdate` (even if there are no changes). This causes unnecessary updates to be reported to developers running `ng update`. Once an update is commited, the CLI will report the update regardless of whether any changes were made or not. This behavior can be observed in the `ng_update_migrations` integration test. See: https://circleci.com/gh/angular/angular/438470#tests/containers/3. Notice how all source files are denoted as `UPDATED` (even though there are no changes). PR Close angular#32391
…ommits empty updates (angular#32391) Commit 904a201 introduced a new migration for undecorated classes with decorated Angular class members. Currently the migration always calls `tree.beginUpdate` and `tree.commitUpdate` (even if there are no changes). This causes unnecessary updates to be reported to developers running `ng update`. Once an update is commited, the CLI will report the update regardless of whether any changes were made or not. This behavior can be observed in the `ng_update_migrations` integration test. See: https://circleci.com/gh/angular/angular/438470#tests/containers/3. Notice how all source files are denoted as `UPDATED` (even though there are no changes). PR Close angular#32391
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Commit 904a201 introduced a new migration for undecorated classes with
decorated Angular class members. Currently the migration always calls
tree.beginUpdate
andtree.commitUpdate
(even if there are no changes).This causes unnecessary updates to be reported to developers running
ng update
.Once an update is committed, the CLI will report the update regardless of whether any
changes were made or not.
This behavior can be observed in the
ng_update_migrations
integration test. See:https://circleci.com/gh/angular/angular/438470#tests/containers/3. Notice how all
source files are denoted as
UPDATED
.