-
Notifications
You must be signed in to change notification settings - Fork 12k
"ng d component <component name>" is not deleting the component reference from app.module.ts and the component folder #1776
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
We don't support destroying generated files. This will be removed from |
@filipesilva Please tell how to delete a component. |
@usama520 you delete the fine manually, and delete all references to it. |
That's not very useful. Either the ng cli should support developing components by adding in the creation and deletion of them, or it should not. But just doing half a job seems pointless, it serves only to demonstrate how it would be useful to have such a tool, and then leaves the user to have to write the tool themselves. |
Why does Angular support generating a component from the CLI, but not deleting one? |
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. |
Linux -Ubuntu 16.04
angular-cli : 1.0.0-beta.11-webpack.2
node : 6.4.0
os : linux x64
ng d component <component_name>
is not deleting component reference from app.module.ts and the folder which containing the deleted component.The text was updated successfully, but these errors were encountered: