From 1184b577400784b0c204768129d3090eb8b986c7 Mon Sep 17 00:00:00 2001 From: Aysegul Yonet Date: Sun, 20 Mar 2016 22:17:09 -0700 Subject: [PATCH] docs: update to style-guide links closes #995 Fixed links to John Papa style guide to new repo location. --- public/docs/ts/latest/guide/upgrade.jade | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/public/docs/ts/latest/guide/upgrade.jade b/public/docs/ts/latest/guide/upgrade.jade index 3a3fa0346f..5b876af92b 100644 --- a/public/docs/ts/latest/guide/upgrade.jade +++ b/public/docs/ts/latest/guide/upgrade.jade @@ -76,13 +76,13 @@ include ../_util-fns There are a few rules in particular that will make it much easier to do *an incremental upgrade* using the Angular 2 `upgrade` module: - * The [Rule of 1](https://github.com/johnpapa/angular-styleguide#single-responsibility) + * The [Rule of 1](https://github.com/johnpapa/angular-styleguide/blob/master/a1/README.md#single-responsibility) states that there should be one component per file. This not only makes components easy to navigate and find, but will also allow us to migrate them between languages and frameworks one at a time. In this example application, each controller, factory, and filter is in its own source file. - * The [Folders-by-Feature Structure](https://github.com/johnpapa/angular-styleguide#style-y152) - and [Modularity](https://github.com/johnpapa/angular-styleguide#modularity) + * The [Folders-by-Feature Structure](https://github.com/johnpapa/angular-styleguide/blob/master/a1/README.md#folders-by-feature-structure) + and [Modularity](https://github.com/johnpapa/angular-styleguide/blob/master/a1/README.md#modularity) rules define similar principles on a higher level of abstraction: Different parts of the application should reside in different directories and Angular modules.