Skip to content

Add --skip-tests flag to ng init #3791

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

Closed
aegyed91 opened this issue Dec 30, 2016 · 3 comments
Closed

Add --skip-tests flag to ng init #3791

aegyed91 opened this issue Dec 30, 2016 · 3 comments
Labels
P5 The team acknowledges the request but does not plan to address it, it remains open for discussion

Comments

@aegyed91
Copy link

It would be nice to have a --skip-tests flag in the ng new / init command.

I know it is a very bad practice to omit writing unit and e2e tests but it would be a useful flag for barbarians like me. 💃

I wanted to know your opinion about it before making a PR.

@filipesilva filipesilva added command: new P5 The team acknowledges the request but does not plan to address it, it remains open for discussion labels Dec 30, 2016
@baruchvlz
Copy link
Contributor

baruchvlz commented Jan 2, 2017

If ng new myApp --skip-tests is run, should the angular-cli.json be updated to change the following:

    "spec": {
      "class": false, 
      "component": true, // change to false
      "directive": true, // change to false
      "module": false,
      "pipe": true, // change to false
      "service": true // change to false
    }

That way the --skip-tests flag will affect the whole project, not just the ng new/init command.

@sumitarora
Copy link
Contributor

Closing as it has been implemented.

@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 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P5 The team acknowledges the request but does not plan to address it, it remains open for discussion
Projects
None yet
Development

No branches or pull requests

5 participants