-
Notifications
You must be signed in to change notification settings - Fork 12k
ng destroy component does not remove component from app.module.ts file #2299
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
Comments
Hey, Im have same issue but cant find any info( |
The |
@filipesilva What's the best way to destroy a generated component or directive then? |
+1 |
In my experience the best way is to use git to figure out what was added. It's usually easy to figure out the new files, but not so easy to figure out the added imports. We've talked about how generators maybe shouldn't auto-add the imports, but haven't decided if it's worth to change it. |
@filipesilva Maybe list the files edited on generating new components + the new files? |
That's a really good idea @MohamadAtieh. We list the created files but don't list the edited ones. I'll make an issue for it. |
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. |
Mac OSX 0.11.6 El Capitan
angular-cli: 1.0.0-beta.15
node: 6.6.0
os: darwin x64
ng new new-app; cd new-app/src/app
ng g component foo
ng destroy component foo
Notice that the src/app/app.module.ts file still has references to the foo component.
The text was updated successfully, but these errors were encountered: