-
Notifications
You must be signed in to change notification settings - Fork 26.1k
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
fix(core): fix ng generate @angular/core:output-migration #60626
Conversation
packages/core/schematics/migrations/output-migration/output-replacements.ts
Outdated
Show resolved
Hide resolved
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.
Looks like we're going in the right direction with this.
Can we also add a test that covers the migration of @Output() eventMovement = new EventEmitter<IResponse>();
?
Also please look at the linting failures, we have a formatting issue. Note: The currently broken tests are flakes and related to this change. |
Sure |
packages/core/schematics/migrations/output-migration/output-replacements.ts
Outdated
Show resolved
Hide resolved
fix lint errors |
We're still missing the test to cover |
I added this test: do I change it? |
My bad, it's an oversight :) |
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.
However, this is outside of my review scope. I'll let Pawel do a 2nd review.
I checked also inputs migration command and seems that behaviour it'ok. That command doesn't have the same bug that the output did. |
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.
Thnx so much for the bug fix, appreciate it ❤️
The logic LGTM, just want to ask you to move tests around.
@pkozlowski-opensource I have updated with what was requested. Thanks for your availability For the rest it's a pleasure |
output-migration command not keep type if @output declaring without initializer
ff4cbfe
to
6461aab
Compare
This PR was merged into the repository by commit cdbc6e8. The changes were merged into the following branches: main, 19.2.x |
output-migration command not keep type if @output declaring without initializer
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?
The output-migration command not keep type if @output declaring without initializer
Issue Number: #59248
What is the new behavior?
The output-migration command keep type
Does this PR introduce a breaking change?