honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(upgrade): rename Angular 2 to Angular (#3169)

This commit is contained in:
Rasmus Reimer 2017-01-31 14:42:47 +01:00 committed by Jesús Rodríguez
parent 03ecf92a88
commit 5c19f174f1
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
public/docs/ts/latest/guide/upgrade.jade
View File

@ -213,7 +213,7 @@ include ../_util-fns
The `upgrade` module in Angular is a very useful tool for upgrading The `upgrade` module in Angular is a very useful tool for upgrading
anything but the smallest of applications. With it we can mix and match anything but the smallest of applications. With it we can mix and match
AngularJS and 2 components in the same application and have them interoperate AngularJS and Angular components in the same application and have them interoperate
seamlessly. That means we don't have to do the upgrade work all at once, seamlessly. That means we don't have to do the upgrade work all at once,
since there's a natural coexistence between the two frameworks during the since there's a natural coexistence between the two frameworks during the
transition period. transition period.
@ -1115,7 +1115,7 @@ code-example(format="").
that we want to load. Since we're bootstrapping the app through that we want to load. Since we're bootstrapping the app through
an `UpgradeModule`, we're actually now running the app as a **hybrid app**. an `UpgradeModule`, we're actually now running the app as a **hybrid app**.
This means we are now running both AngularJS and 2 at the same time. That's pretty This means we are now running both AngularJS and Angular at the same time. That's pretty
exciting! We're not running any actual Angular components yet though, exciting! We're not running any actual Angular components yet though,
so let's do that next. so let's do that next.
@ -1210,7 +1210,7 @@ code-example(format="").
Now that we are loading `phone.service.ts` through an import that is resolved Now that we are loading `phone.service.ts` through an import that is resolved
by SystemJS, we should **remove the <script> tag** for the service from `index.html`. by SystemJS, we should **remove the <script> tag** for the service from `index.html`.
This is something we'll do to all our components as we upgrade them. Simultaneously This is something we'll do to all our components as we upgrade them. Simultaneously
with the AngularJS to 2 upgrade we're also migrating our code from scripts to modules. with the AngularJS to Angular upgrade we're also migrating our code from scripts to modules.
At this point we can switch our two components to use the new service At this point we can switch our two components to use the new service
instead of the old one. We `$inject` it as the downgraded `phone` factory, instead of the old one. We `$inject` it as the downgraded `phone` factory,