You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature: When generating a NgModule, allow -m to indicate which NgModule should import it #5377
ng g m login -m app.module doesn't look for the -m option today . But i think it would be helpful to be able to create a NgModule and tell the CLI where you want it imported (in another module).
Without this, today we must manually import it.
This would allow it to work similar to how ng g s data -m some.module and ng g c customer -mother.module work today
Activity
feat(@angular/cli): add import flag to modules
feat(@angular/cli): add import flag to modules
feat(@angular/cli): add import flag to modules
feat(@angular/cli): add import flag to modules
feat(@angular/cli): add import flag to modules
feat(@angular/cli): add import flag to modules
feat(@angular/cli): add import flag to modules
feat(@angular/cli): add import flag to modules
feat(@angular/cli): add import flag to modules
feat(@angular/cli): add import flag to modules
feat(@angular/cli): add import flag to modules
feat(@angular/cli): add import flag to modules
feat(@angular/cli): add import flag to modules
angular-automatic-lock-bot commentedon Sep 7, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
feat(@angular/cli): add import flag to modules