CopyPastor

Detecting plagiarism made easy.

Score: 0.9044917225837708; Reported for: String similarity Open both answers

Possible Plagiarism

Plagiarized on 2017-05-30
by Arvind Audacious

Original Post

Original - Posted on 2016-12-28
by Brocco



            
Present in both answers; Present only in the new answer; Present only in the old answer;

destroy or something similar may come to the CLI, but it is not a primary focus at this time. So you will need to do this manually.
Delete the component directory (assuming you didn't use --flat) and then remove it from the NgModule in which it is declared.
If you are unsure of what to do, I suggest you have a "clean" app meaning no current git changes. Then generate a component and see what is changed in the repo so you can backtrack from there what you will need to do to delete a component.
`destroy` or something similar may come to the CLI, but it is not a primary focus at this time. So you will need to do this manually.
Delete the component directory (assuming you didn't use `--flat`) and then remove it from the `NgModule` in which it is declared.
If you are unsure of what to do, I suggest you have a "clean" app meaning no current `git` changes. Then generate a component and see what is changed in the repo so you can backtrack from there what you will need to do to delete a component.

Update ------
If you're just experimenting about what you want to generate, you can use the `--dry-run` flag to not produce any files on disk, just see the updated file list.

        
Present in both answers; Present only in the new answer; Present only in the old answer;