Skip to content

Feature Request: ng generate --sass Flag To Generate SCSS File #1177

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
griffiti opened this issue Jun 23, 2016 · 4 comments
Closed

Feature Request: ng generate --sass Flag To Generate SCSS File #1177

griffiti opened this issue Jun 23, 2016 · 4 comments
Labels
P5 The team acknowledges the request but does not plan to address it, it remains open for discussion

Comments

@griffiti
Copy link

It would be nice to have a --sass flag to use with ng generate to create a .scss file instead of a .css file for a given component.

ng generate component user-list.component --sass

@filipesilva filipesilva added type: enhancement P5 The team acknowledges the request but does not plan to address it, it remains open for discussion labels Jul 4, 2016
@masaanli
Copy link

masaanli commented Jul 6, 2016

@griffiti You know there is a possibility to set the default style extension inside the 'angular-cli.json' file.

styleExt: 'scss' for example, if you do that it will generate a .scss file instead of a .css file with the generation of a component or route for example.

@gfrSE
Copy link

gfrSE commented Aug 16, 2016

use ng set defaults.styleExt scss

@filipesilva
Copy link
Contributor

I'm closing this issue because the answers given here seem to cover the usecase, and I don't see a big need to support it on the ng generate component command.

It doesn't sound common enough that a user would have a default on angular-cli.json and then use a few different preprocessors elsewhere in the app.

@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

4 participants