iSharkFly-Docs/angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(aio): add relative to app level routes section (#26504)

Browse Source 
Added word *relative* to the **Routes at the app level** section description. This was not specified before. The routes in the *lazy-loading-ngmodules/src/app/app-routing.module.ts* also had `loadChildren` values starting with `app/...`.

The code for `app-routing.module.ts` is already fixed in [this commit](https://github.com/angular/angular/commit/67ad9468d35fee9e0b0f829d18d01eafda251f1e)
PR Close #26504
This commit is contained in:
Siddharth Ajmera
2018-10-17 16:02:47 +05:30
committed by Miško Hevery
parent a609bf50ed
commit 665627e254
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
aio/content/guide/lazy-loading-ngmodules.md
+1 -1
View File
@@ -143,7 +143,7 @@ In `AppRoutingModule`, update the `routes` array with the following:
</code-example>
The import statements stay the same. The first two paths are the routes to the `CustomersModule` and the `OrdersModule` respectively. Notice that the lazy loading syntax uses `loadChildren` followed by a string that is the path to the module, a hash mark or `#`, and the module’s class name.
The import statements stay the same. The first two paths are the routes to the `CustomersModule` and the `OrdersModule` respectively. Notice that the lazy loading syntax uses `loadChildren` followed by a string that is the relative path to the module, a hash mark or `#`, and the module’s class name.
### Inside the feature module