Default schematics options with uppercase doesn't work

[cyrilletuzi]

Versions

cli v6.0.0-rc.5

Repro steps

• npm install @angular/cli@next
• ng new helloworld --inline-template
• cd helloworld
• ng g generate test

Observed behavior

Produce a component with external template.

Desired behavior

Produce a component with inline template.

Mention any other details that might be useful (optional)

I did some investigation:

• ng g component test --inline-template works
• following feat(@schematics/angular): save ng new options as defaults devkit#666, default options are rightly saved in angular.json:

"schematics": {
    "@schematics/angular:component": {
      "inlineTemplate": true
    }
}

• adding other options in lowercase like spec works:

"schematics": {
    "@schematics/angular:component": {
      "spec": false
    }
}

• adding other options with uppercase letters like skipImport doesn't work:

"schematics": {
    "@schematics/angular:component": {
      "skipImport": true
    }
}

So I think the defaults options of angular.json with uppercase letters are wrongly transformed/passed to the generation command.

I think it's a quick PR I can do, but I don't know where the problem happen...

[cyrilletuzi]

@filipesilva @clydin Any workaround idea? I have an Angular 6 course on Wednesday, I've managed to find workarounds for all other issues remaining in CLI v6, but I don't find any solution for this one, which would be quite inconvenient.

[cyrilletuzi]

@hansl @Brocco @filipesilva I know it may be a low priority on your side, but it's very inconvenient during Angular courses (external templates mean switching between a lot of files, and students are lost). And everyone relying on this previously will consider this as a regression. Can you please consider fixing this for v6? I think it's a really quick fix when you know where the options are managed. Thanks.

[cyrilletuzi]

PR in #10570

[angular-automatic-lock-bot]

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.}