fix(core): Fixed inject migration schematics for migrate destructured properties#62832
fix(core): Fixed inject migration schematics for migrate destructured properties#62832aparzi wants to merge 1 commit intoangular:mainfrom
Conversation
d978f3c to
ff3fcf4
Compare
|
Fixed lint |
packages/core/schematics/ng-generate/inject-migration/migration.ts
Outdated
Show resolved
Hide resolved
ff3fcf4 to
0dfe02b
Compare
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request fixes a bug in the inject migration schematic to correctly handle destructured properties in constructor parameters. The implementation introduces a ParameterMigrationContext to group related parameters, refactors the main migration function to handle different parameter kinds, and adds logic to correctly transform destructured properties into class properties with inject(). A new test case is also added to cover this scenario. The changes are well-structured and the fix appears correct. I have one minor suggestion to improve code clarity.
packages/core/schematics/ng-generate/inject-migration/migration.ts
Outdated
Show resolved
Hide resolved
packages/core/schematics/ng-generate/inject-migration/migration.ts
Outdated
Show resolved
Hide resolved
packages/core/schematics/ng-generate/inject-migration/migration.ts
Outdated
Show resolved
Hide resolved
0dfe02b to
7b38c50
Compare
|
@JeanMeche fixed lint and made the requested changes |
packages/core/schematics/ng-generate/inject-migration/migration.ts
Outdated
Show resolved
Hide resolved
7b38c50 to
3a970bc
Compare
… properties Fixes angular#62626 - Properties used with the destructor are also managed during migration.
3a970bc to
04885c8
Compare
|
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. |
Fixed inject migration schematics for migrate destructured properties
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?
Issue Number: #62626
What is the new behavior?
Fixed inject migration schematics for migrate destructured properties
Does this PR introduce a breaking change?