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
Copy file name to clipboardExpand all lines: README.md
+2-18Lines changed: 2 additions & 18 deletions
Original file line number
Diff line number
Diff line change
@@ -102,25 +102,9 @@ Enum | `ng g enum my-new-enum`
102
102
103
103
### Generating a route
104
104
105
-
You can generate a new route with the following command (note the singular
106
-
used in `hero`):
105
+
Generating routes in the CLI has been disabled for the time being. A new router and a new route generation blueprints are coming.
107
106
108
-
```bash
109
-
ng generate route hero
110
-
```
111
-
112
-
This will create a folder which will contain the hero component and related test and style files.
113
-
114
-
The generated route will also be registered with the parent component's `@RouteConfig` decorator.
115
-
116
-
By default the route will be designated as a **lazy** route which means that it will be loaded into the browser when needed, not upfront as part of a bundle.
117
-
118
-
In order to visually distinguish lazy routes from other routes the folder for the route will be prefixed with a `+` per the above example the folder will be named `+hero`.
119
-
This is done in accordance with the [style guide](https://angular.io/styleguide#!#prefix-lazy-loaded-folders-with-).
120
-
121
-
The default lazy nature of routes can be turned off via the lazy flag (`--lazy false`)
122
-
123
-
There is an optional flag for `skip-router-generation` which will not add the route to the parent component's `@RouteConfig` decorator.
107
+
You can read the overview of the new Router here: http://victorsavkin.com/post/145672529346/angular-router. Please note that even though route generation is disabled, building your projects with routing is still fully supported.
0 commit comments