fix(core): fix removal of a container reference used in the component…#60210
fix(core): fix removal of a container reference used in the component…#60210aparzi wants to merge 1 commit intoangular:mainfrom
Conversation
|
Could you please capture the fix in a unit test in Thank you. |
Hi @JeanMeche I Integrated unit test, based on the issue template |
packages/core/schematics/ng-generate/control-flow-migration/util.ts
Outdated
Show resolved
Hide resolved
|
Hi @JeanMeche, Thanks. |
packages/core/schematics/ng-generate/control-flow-migration/util.ts
Outdated
Show resolved
Hide resolved
packages/core/schematics/ng-generate/control-flow-migration/util.ts
Outdated
Show resolved
Hide resolved
JeanMeche
left a comment
There was a problem hiding this comment.
Beside the nit, LGTM.
Would also like to have @thePunderWoman's approval on this!
Ok @JeanMeche I'll make the improvement as soon as possible. Thanks |
packages/core/schematics/ng-generate/control-flow-migration/util.ts
Outdated
Show resolved
Hide resolved
… file During migration a container reference was deleted even though it was used in the component file.
thePunderWoman
left a comment
There was a problem hiding this comment.
LGTM! Thank you for taking the time to fix this and to add the unit tests.
|
Caretaker note: presubmit failures are flakes. This is safe to merge. |
|
This PR was merged into the repository by commit de2bfc0. The changes were merged into the following branches: main, 19.2.x |
|
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. |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
ng generate @angular/core:control-flow migration removes the container reference even if it is used in component file
Issue Number: #56565
What is the new behavior?
During migration a container reference was deleted even though it was used in the component file.
Does this PR introduce a breaking change?