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
Revert 'fix(@schematics/angular): stop offering SASS option for ng new #13444' #13739
Comments
@nex3 can you give Angular team some guidance about whether Indented Sass (.sass files) should be considered "deprecated"? Should we stop creating new Angular projects using the old syntax? |
As far as the Sass team is concerned, the indented syntax is fully supported. |
Thanks @nex3! We'll re-introduce support for generating apps in that syntax |
…ention Sass Indented (.sass) is fully supported by the Sass team and we should still offer and support it. Fixes #13739
Somewhat ironically, and after switching to scss because I was forced to, I now prefer it in some cases |
…ention Sass Indented (.sass) is fully supported by the Sass team and we should still offer and support it. Fixes #13739
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
I initially thought this was a bug!
ng g c component-name --style=sass
generates .scss filesng new my-project --style=sass
generates .scss filesWhat is the reason behind this change?
What about those of us who prefer using the sass indented syntax? It is still supported and they are not dropping it so I don't see any reason to remove it from ng generate and ng new simply because most developers prefer the scss syntax.
This is really causing a problem for my workflow as I am using
let g:angular_cli_stylesheet_format = 'sass'
in my .vimrc so I now have to convert everything to scss and start working with syntax I don't like to use.#13444
@andyg3
The text was updated successfully, but these errors were encountered: