ng generate does not respect defaults.styleExt settings

[onwsk8r]

- [x] bug report -> please search issues before submitting
- [ ] feature request

Versions.

> ng --version
@angular/cli: 1.4.1
node: 6.11.3
os: linux x64
@angular/animations: 4.3.6
@angular/common: 4.3.6
@angular/compiler: 4.3.6
@angular/core: 4.3.6
@angular/forms: 4.3.6
@angular/http: 4.3.6
@angular/platform-browser: 4.3.6
@angular/platform-browser-dynamic: 4.3.6
@angular/router: 4.3.6
@angular/cli: 1.4.1
@angular/compiler-cli: 4.3.6
@angular/language-service: 4.3.6
typescript: 2.3.4
> npm --version
3.10.10

Repro steps.

After setting the default....

> ng set --global defaults.styleExt=scss
> grep styleExt ~/angular-cli.json
    "styleExt": "scss"

When I make a new project...

> ng new my_proj && cd my_proj
...
> grep styleExt ./.angular-cli.json
    "styleExt": "scss", 

I have a file called app.component.scss with the correct styleUrl in app.component.ts.

However, when I ng g component my-awesome-component, I end up with my-awesome.component.css and the equivalent styleUrl in the Typescript file.

Desired functionality.

I would like it to respect the settings in .angular-cli.json like ng new does.

[alaindeurveilher]

It is not only the styleExt property, but also the prefix property which is ignored.
in my .angular-cli.json I have

{
  "apps": [
    {
      "prefix": "ts",
    }
  ],
  "defaults": {
    "styleExt": "scss",
    "component": {}
  }
}
"

but when generating a new component ng g +my-module/new-component I end up with a .css file instead of a .scss as already reported, but also the component selector is app-new-component instead of ts-new-component

I think that this is a serious regression compared to v1.3.2

[bboehm86]

Actually all defaults are ignored in the .angular-cli.json file. If you use the options directly in the command line everything still works file.

[VirajNimbalkar]

Same with me, I raised issue over SO for this, Here is link , https://stackoverflow.com/questions/46139997/angular-cli-1-4-1-ng-always-generate-spec-file-and-css-even-default-prefix-is

I thought , its only with me, but seems CLI team broke things very seriously here. I hope by downgrading it solve temporary.

[shmool]

The style extension issue was already reported here: #7624

@Brocco I believe there is a problem with the schematics library.
I found two troublesome commits, tested with the command ng g c test:

128187e
Problems that started here:

1. default style extension ignored
2. alias c doesn't work, using component does.

884385e

1. alias c came back to life
2. default style extension is still ignored
3. default inlineTemplate is ignored starting from this commit

Hope this helps! :)

[rafaelss95]

Dupe of #7624

[onwsk8r]

Even though this is a dupe I'm going to leave it open since #7647 will close this when it gets merged (and as of now, Travis is passing, so it just needs a review). And sorry for posting a dupe- I'm not sure how I missed 7624.