-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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(angular): add parent flag to ngrx generator #14105
feat(angular): add parent flag to ngrx generator #14105
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
): void { | ||
const modulePath = options.module; | ||
const sourceText = tree.read(modulePath, 'utf-8'); | ||
const parentPath = options.module ?? options.parent; |
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.
nit: since both module and parent are optional now but I think we have to have at least either one. parent
will be made required as we remove module
in the future but can/should we put a check for them here, and log an actionable error message for now?
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
We currently only have the flag
--module
for the NgRx generator, however, this does not make sense with Standalone Components.Expected Behavior
Deprecate the
--module
flag in favour of the new--parent
flag.--parent
flag behaviour will mimic--module
for now, but will eventually be expanded to include support for Standalone Components