Skip to content
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

chore(commands): override ng destroy #2739

Closed
wants to merge 1 commit into from

Conversation

filipesilva
Copy link
Contributor

It's common for users to try and do ng destroy component name and have
it only partially work.

Since we don't support the command, it's better to not have it do any
partial operations.

@Brocco
Copy link
Contributor

Brocco commented Oct 18, 2016

Just clean up the linting errors so CI will pass.

It's common for users to try and do `ng destroy component name` and have
it only partially work.

Since we don't support the command, it's better to not have it do any
partial operations.
filipesilva added a commit that referenced this pull request Oct 18, 2016
It's common for users to try and do `ng destroy component name` and have
it only partially work.

Since we don't support the command, it's better to not have it do any
partial operations.

Close #2739
kieronqtran pushed a commit to kieronqtran/angular-cli that referenced this pull request Oct 21, 2016
It's common for users to try and do `ng destroy component name` and have
it only partially work.

Since we don't support the command, it's better to not have it do any
partial operations.

Close angular#2739
@filipesilva filipesilva deleted the remove-destroy branch October 22, 2016 10:04
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants