Hopiu/angular.js
1
0
Fork 0
mirror of https://github.com/Hopiu/angular.js.git synced 2026-05-23 21:35:47 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fixes some links and types in the DI docs.

Browse source
This commit is contained in:
Pepper Lebeck-Jobe 2011-03-20 21:49:06 -07:00 committed by Igor Minar
parent e1d122a4b7
commit 4da65d0e8c
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
docs/guide.di.ngdoc
View file

@ -111,7 +111,7 @@ for isolation reasons. We get this isolation by having each test create its own
<pre> <pre>
// crate a root scope // crate a root scope
var rootScope = angular.scope(); var rootScope = angular.scope();
// accesss the service loctor // accesss the service locator
var myService = rootScope.$service('myService'); var myService = rootScope.$service('myService');
</pre> </pre>
@ -136,7 +136,7 @@ MyController.$inject = ['$route'];
</pre> </pre>
In this example, the `MyController` constructor function takes one argument, the In this example, the `MyController` constructor function takes one argument, the
(@link angular.service.$route $route) service. Angular is then responsible for supplying the {@link angular.service.$route $route} service. Angular is then responsible for supplying the
instance of `$route` to the controller when the constructor is instantiated. There are two ways to instance of `$route` to the controller when the constructor is instantiated. There are two ways to
cause controller instantiation – by configuring routes with the $route service or by referencing the cause controller instantiation – by configuring routes with the $route service or by referencing the
controller from the HTML template, such as: controller from the HTML template, such as:
@ -260,8 +260,8 @@ rootScope.$service(greet, fnThis, 'world');
# Inferring `$inject` # Inferring `$inject`
** EXPERIMENTAL: this is an experimental feature, see the important note at the end of this section **EXPERIMENTAL: this is an experimental feature, see the important note at the end of this section
for drawbacks. ** for drawbacks.**
We resort to `$inject` and our own annotation because there is no way in JavaScript to get a list of We resort to `$inject` and our own annotation because there is no way in JavaScript to get a list of
arguments. Or is there? It turns out that calling `.toString()` on a function returns the function arguments. Or is there? It turns out that calling `.toString()` on a function returns the function
@ -286,7 +286,7 @@ fnA.$inject = ['$window', 'serviceA'];
// inject '$window', 'serviceA', curry 'name'; // inject '$window', 'serviceA', curry 'name';
function fnB($window, serviceA_, name){}; function fnB($window, serviceA_, name){};
// implies: fnA.$inject = ['$window', 'serviceA']; // implies: fnB.$inject = ['$window', 'serviceA'];
</pre> </pre>
If angular does not find an `$inject` annotation on the function, then it calls the `.toString()` If angular does not find an `$inject` annotation on the function, then it calls the `.toString()`
@ -301,4 +301,4 @@ and tries to infer what should be injected using the following rules:
Minifiers/obfuscators change the names of function arguments and will therefore break the `$inject` Minifiers/obfuscators change the names of function arguments and will therefore break the `$inject`
inference. For this reason, either explicitly declare the `$inject` or do not use inference. For this reason, either explicitly declare the `$inject` or do not use
minifiers/obfuscators. In the future, we may provide a pre-processor which will scan the source code minifiers/obfuscators. In the future, we may provide a pre-processor which will scan the source code
and insert the `$inject` into the source code so that it can be minified/obfuscated. and insert the `$inject` into the source code so that it can be minified/obfuscated.