ng new --prefix kebap-case causes lint errors in directives

[pa-ru]

🐞 Bug report

Command (mark with an x)

- [x] new

Is this a regression?

unknown but probably not

Description

If you create a new app with ng new --prefix compony-domain the prefix results in the following
tslint.json is generated:

{
    "extends": "../tslint.json",
    "rules": {
        "directive-selector": [
            true,
            "attribute",
            "company-domain",
            "camelCase"
        ],
        "component-selector": [
            true,
            "element",
            "company-domain",
            "kebab-case"
        ]
    }
}

If you create a new directive with ng g d highlight the resulting selector is companyDomainHighlight and causes lint errors.

🔬 Minimal Reproduction

• ng new kebap-case --prefix kebap-case
• ng g d highlight
• ng lint

🔥 Exception or Error

$ ng lint
Linting "kebap-case"...

ERROR: D:/src/kebap-case/src/app/highlight.directive.ts[4, 13]: The selector of the directive "HighlightDirective" should have prefix "kebap-case" (https://angular.io/styleguide#style-02-08)

Lint errors found in the listed files.

🌍 Your Environment

Angular CLI: 7.3.4
Node: 8.14.0
OS: win32 x64
Angular: 7.2.7
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.13.4
@angular-devkit/build-angular     0.13.4
@angular-devkit/build-optimizer   0.13.4
@angular-devkit/build-webpack     0.13.4
@angular-devkit/core              7.3.4
@angular-devkit/schematics        7.3.4
@angular/cli                      7.3.4
@ngtools/webpack                  7.3.4
@schematics/angular               7.3.4
@schematics/update                0.13.4
rxjs                              6.3.3
typescript                        3.2.4
webpack                           4.29.0

Anything else relevant?

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