Rename / remove / move components

[zpydee]

Please provide us with the following information:

1. OS? Mac OSX (El Capitan)

1. Versions. Please run ng --version. If there's nothing outputted, please
   angular-cli: 1.0.0-beta.1
   node: 5.7.0
   os: darwin x64

It would be really usefull to add cli commands for:

• rm = removing a component
• mv = moving / renaming a component

Unless I am missing it, I don't see that this exists and it would be really useful during refactoring to avoid all the manual updates that come with this process.

Thoughts?

[sWW26]

ember-cli has ember destroy for removing items.

And there's an afterUninstall hook that can be used to remove barrel registration.

[filipesilva]

ember-cli indeed does have those commands, but they currently are not working correctly with the blueprints.

[kylecordes]

Here's a bit of further feedback. The current way that CLI creates new components and other pieces has the merit of following the nascent style guide. So perhaps this feedback is really for the style guide. It certainly creates quite a lot of duplication and naming. For everything that we add using this tooling, we get N copies of its name across multiple directories and files, with two different variations of the name. When the time comes to rename (which happens quite often in real applications), this adds lots of friction. I suppose there is nothing to be done about it; the decision has already been made that the official style will be to use two different variations of every name (or more) and to spray them across many files. But there certainly is an opportunity for the CLI to ease the trouble that this decision creates.

[filipesilva]

Somewhat related issue: #357

@kylecordes overall refactoring of typescript projects is quite well supported across different IDEs via typescript services. Refactoring a name should operate correctly across the project, and disregarding other variables with the same name.

I'm also not too clear what you mean by "N copies of its name" and "two different variations of every name", but you are right that those are style guide decisions and not CLI decisions - the CLI merely implements the style guide to the best of it's ability.

[pramttl]

Renaming a component would be very useful to have CLI feature. I was expecting this feature to be there and saw the CLI help and was disappointed because it wasn't.

I have to rename atleast 5-6 files (*.component.ts, *.scss, *spec.ts, *.service.ts, etc) and then update those files where the component was imported or used. (e.g. app.routes.ts and other files). A quick CLI command for this would be a big timesaver.

[heysushil]

I didn't get the solution for - how to remove component by angular-cli . I was tried my examples but still get nothing ! rm and mv didn't worked ?

[leehericks]

A ng destroy would be a good opposite of ng generate as the readme introduces generate like ng generate component my-new-component which creates MyNewComponentComponent.

[solanoepalacio]

I as well believe a ng destroy would be quite usefull

[Gastalver]

+1 to ng destroy or ng remove