This repository was archived by the owner on Dec 4, 2017. It is now read-only.
File tree 1 file changed +3
-3
lines changed
public/docs/ts/latest/guide
1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -76,13 +76,13 @@ include ../_util-fns
76
76
There are a few rules in particular that will make it much easier to do
77
77
*an incremental upgrade* using the Angular 2 `upgrade` module:
78
78
79
- * The [Rule of 1](https://github.com/johnpapa/angular-styleguide#single-responsibility)
79
+ * The [Rule of 1](https://github.com/johnpapa/angular-styleguide/blob/master/a1/README.md #single-responsibility)
80
80
states that there should be one component per file. This not only makes
81
81
components easy to navigate and find, but will also allow us to migrate
82
82
them between languages and frameworks one at a time. In this example application,
83
83
each controller, factory, and filter is in its own source file.
84
- * The [Folders-by-Feature Structure](https://github.com/johnpapa/angular-styleguide#style-y152 )
85
- and [Modularity](https://github.com/johnpapa/angular-styleguide#modularity)
84
+ * The [Folders-by-Feature Structure](https://github.com/johnpapa/angular-styleguide/blob/master/a1/README.md#folders-by-feature-structure )
85
+ and [Modularity](https://github.com/johnpapa/angular-styleguide/blob/master/a1/README.md #modularity)
86
86
rules define similar principles on a higher level of abstraction: Different parts of the
87
87
application should reside in different directories and Angular modules.
88
88
You can’t perform that action at this time.
0 commit comments