Skip to content

Project Settings - allow config level values for spec generation settings #2448

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
Brocco opened this issue Sep 30, 2016 · 2 comments · Fixed by #2475
Closed

Project Settings - allow config level values for spec generation settings #2448

Brocco opened this issue Sep 30, 2016 · 2 comments · Fixed by #2475
Assignees

Comments

@Brocco
Copy link
Contributor

Brocco commented Sep 30, 2016

In angular-cli.json under defaults add:

"spec": {
  "class": [true/false],
  "component": [true/false],
  "directive": [true/false],
  "module": [true/false],
  "pipe": [true/false],
  "service": [true/false]}

When generating blueprints the precedence will be:

  • command-line option value if specified
  • value in configuration file
  • current default value for each blueprint specified to maintain current functionality
@Brocco Brocco self-assigned this Sep 30, 2016
@Brocco
Copy link
Contributor Author

Brocco commented Oct 1, 2016

Awaiting Issue #2447 (via PR #2457) as changes to configuration will be needed to make this similar change.

@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
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant