Repository navigation
New project generates incorrect routing export/import name with --routing #2433
Description
Please provide us with the following information:
OS?
Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
OSX Yosemite
Versions.
Please run
ng --version. If there's nothing outputted, please run in a Terminal:node --versionand paste the result here:
angular-cli: 1.0.0-beta.16
node: 5.12.0
os: darwin x64
Repro steps.
Was this an app that wasn't created using the CLI? What change did you do on your code? etc.
Run ng new testapp --routing
The app-routing.module.ts file is generated with export class TestappRoutingModule { } instead of export class AppRoutingModule { }
The app.module.ts import is incorrect for the routing file.
import { TestappRoutingModule } from './testapp-routing.module';
instead of
import { AppRoutingModule } from './app-routing.module';
The log given by the failure.
Normally this include a stack trace and some more information.
Mention any other details that might be useful.
Thanks! We'll be in touch soon.
Activity
hantsy commentedon Sep 30, 2016
I encountered this same issue under Windows 10 64bit.
Windows 10, NodeJS 6.7, Angular CLI 1.0.0-beta.16
bug(route): fix the class names for --routing in ng new
bug(route): fix the class names for --routing in ng new
bug(route): fix the class names for --routing in ng new (#2435)
bug(route): fix the class names for --routing in ng new (angular#2435)
bug(route): fix the class names for --routing in ng new (angular#2435)
angular-automatic-lock-bot commentedon Sep 6, 2019
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.
fix(@nguniversal/common): correctly handle lazy loaded routes in Clover
bug(route): fix the class names for --routing in ng new (angular#2435)