You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ng new <project-name> -- Using "." or "_" in"project-name" produces errors. #11051
<!-- 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)
Reacted by GAURAV JAIN, Madhav Patel, Suhas Bharadwaj, Geronimo Romney and Mehmet Akif DERE
Reacted by Wogan, Jongz Puangput, Damien Flury, Robert Santana, Suhas Bharadwaj and Mehmet Akif DERE
We use App.projectname for everything. Now dead in water.
Reacted by Robert Santana, ElsassLegend, David Liang, Chuck Dunn, Marcos Latchuk, Benjamin Crosnier, Walter Johnson, Laurent Schwitter, Madhav Patel, David Do and 1 more
So far I'm managing to work around this by renaming the created folder after it has been scaffolded.
So hope it helps those that land here while this is still open. :)
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.
Reacted by rr20eid10, Luiz Felipe Machado da Silva, Eddie Appell, Marcos Latchuk, Pawel, THWU, Nguyễn Dung, Nishan Chathuranga Wickramarathna, Mihai Alexandru-Ionut, Sean and 4 more
@sachin hedaoo If you are reading online “Angular 2” this really refers to the remake of AngularJS in typescript. Even the latest version of angular (which is 7.x iirc) can be referred to as Angular 2.
Essentially, Angular 2 can refer to Angular 2.0.0 but this doesn't really happen anymore (in my limited experience).
On Mar 29, 2019, at 05:49, Kristian Thy ***@***.***> wrote:
Can we install Angular 2.0.0 Version .
I guess you could. Long-term support for 2.x.x ended several years ago though, so I'm not sure why you would.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
Activity
rafaelss95 commentedon Jun 3, 2018
It seems that it produces error for any special char. I've tested it with
-and/also.john-dieter commentedon Jun 15, 2018
We use App.projectname for everything. Now dead in water.
kvloover commentedon Jul 5, 2018
So far I'm managing to work around this by renaming the created folder after it has been scaffolded.
So hope it helps those that land here while this is still open. :)
kthy commentedon Sep 12, 2018
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.
pranavavva commentedon Oct 18, 2018
Maybe add a feature where if you want to include
.or_in the project name, you can enclose it in quotes. Ex:sachinhd517 commentedon Mar 28, 2019
Can we install Angular 2.0.0 Version . How to install Angular 2 using CLI and which command we will write in CLI specific command.
kthy commentedon Mar 29, 2019
I guess you could. Long-term support for 2.x.x ended several years ago though, so I'm not sure why you would.
pranavavva commentedon Mar 29, 2019
3 remaining items
feat(@schematics/angular): loosen project name validation
angular-automatic-lock-bot commentedon Dec 17, 2021
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.