-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
feat(component): add migration for replacing ReactiveComponentModule #3506
feat(component): add migration for replacing ReactiveComponentModule #3506
Conversation
✅ Deploy Preview for ngrx-io canceled.Built without sensitive environment variables
|
const expected = ` | ||
import { LetModule, PushModule } from '@ngrx/component'; | ||
|
||
const reactiveComponentModule: ReactiveComponentModule; |
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.
I'm not migrating assignments to ReactiveComponentModule
. However, currently I am not preserving the import. This PR could be enhanced by preserving the import of ReactiveComponentModule
when it has not been replaced in the file.
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.
I think it should be preserved in this case.
A migration shouldn't break an application (Ideally 😅).
If it's hard to do that, I would prefer to keep the ReactiveComponentModule
import for all cases.
Will complete this week, I got lost in work but got re-invigorated at ng-conf 😄 |
...little swamped so probably will only get to revisit this weekend or later. Public commitments, amirite 😅. |
…t-module-migration
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.
Great work @david-shortman! This migration will be released in v15. A few suggestions regarding that 👇
Co-authored-by: Marko Stanimirović <markostanimirovic95@gmail.com>
The |
const expected = ` | ||
import { ReactiveComponentModule, LetModule, PushModule } from '@ngrx/component'; | ||
|
||
const reactiveComponentModule: ReactiveComponentModule; |
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.
The changes in this PR look good to me, but....
Seeing this line of code raised a question.
The ReactiveComponentModule
is currently deprecated, do we want to remove that in v15?
If that's the case, should we add a comment above this line to mention that ReactiveComponentModule is removed (can be done in a separate PR)?
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.
I think we can remove ReactiveComponentModule
in v15. I also like the idea of adding a comment about its removal 👍
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.
I like deleting code ;D. I can open a separate PR.
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.
Thank you @david-shortman!! 🥇
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?
Closes #3491
What is the new behavior?
Does this PR introduce a breaking change?
Other information