ng new <project-name> -- Using "." or "_" in"project-name" produces errors.

Versions

Angular CLI: 6.0.5 Node: 10.2.1 OS: win32 x64 Angular: …

Package Version

@angular-devkit/architect 0.6.5 @angular-devkit/core 0.6.5 @angular-devkit/schematics 0.6.5 @schematics/angular 0.6.5 @schematics/update 0.6.5 rxjs 6.2.0 typescript 2.7.2

Windows 10

Repro steps

• ng new project.1
• ng new project_1

Observed behavior

<!-- Normally this includes a stack trace and some more information. -->
-------------------------------------------------------------
$ ng new project.1
Project name "project.1" is invalid.
-------------------------------------------------------------
$ ng new project_1
Schematic input does not validate against the Schema: {"name":"project_1","version":"6.0.5","newProjectRoot":"projects","skipInstall":false,"linkCli":false,"skipGit":false,"commit":null}
Errors:

  Data path ".name" should match format "html-selector".
-------------------------------------------------------------


### Desired behavior
<!--
What would like to see implemented?
What is the usecase?
What did you expect to see?
-->

* Expect "." or "_" to be valid characters in a project name as was in the case in older versions of CLI.

### Mention any other details that might be useful (optional)

[kthy]

So far I’m managing to work around this by renaming the created folder after it has been scaffolded.

ng new FooBar --directory Foo.Bar

works for me in the sense that I don’t need to rename the directory afterwards. The project is still referred to as FooBar rather than Foo.Bar in all the template files of course.

[john-dieter]

We use App.projectname for everything. Now dead in water.