diff options
| author | Igor Minar | 2012-06-11 23:49:24 -0700 |
|---|---|---|
| committer | Igor Minar | 2012-06-12 00:10:18 -0700 |
| commit | f16150d5f1b20b3d633b4402095ea89baa4be042 (patch) | |
| tree | 9d5c570348264884174ecca52b958da7a821fcf8 /docs/content/guide/expression.ngdoc | |
| parent | fc0b2b5715655a05cbb4c8e79969c95d7e7ce8b7 (diff) | |
| download | angular.js-f16150d5f1b20b3d633b4402095ea89baa4be042.tar.bz2 | |
docs(*): simplify doc urls
we now have two types of namespaces:
- true namespace: angular.* - used for all global apis
- virtual namespace: ng.*, ngMock.*, ... - used for all DI modules
the virual namespaces have services under the second namespace level (e.g. ng.)
and filters and directives prefixed with filter: and directive: respectively
(e.g. ng.filter:orderBy, ng.directive:ngRepeat)
this simplifies urls and makes them a lot shorter while still avoiding name collisions
Diffstat (limited to 'docs/content/guide/expression.ngdoc')
| -rw-r--r-- | docs/content/guide/expression.ngdoc | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/content/guide/expression.ngdoc b/docs/content/guide/expression.ngdoc index 28edcc22..770e356e 100644 --- a/docs/content/guide/expression.ngdoc +++ b/docs/content/guide/expression.ngdoc @@ -3,7 +3,7 @@ @description Expressions are JavaScript-like code snippets that are usually placed in bindings such as `{{ -expression }}`. Expressions are process by the {@link api/angular.module.ng.$parse $parse} +expression }}`. Expressions are process by the {@link api/ng.$parse $parse} service. For example, these are all valid expressions in angular: @@ -35,7 +35,7 @@ differences: If, on the other hand, you do want to run arbitrary JavaScript code, you should make it a controller method and call the method. If you want to `eval()` an angular expression from -JavaScript, use the {@link api/angular.module.ng.$rootScope.Scope#$eval `$eval()`} method. +JavaScript, use the {@link api/ng.$rootScope.Scope#$eval `$eval()`} method. ## Example <doc:example> @@ -92,7 +92,7 @@ You can try evaluating different expressions here: # Property Evaluation Evaluation of all properties takes place against a scope. Unlike JavaScript, where names default -to global window properties, angular expressions have to use {@link api/angular.module.ng.$window +to global window properties, angular expressions have to use {@link api/ng.$window `$window`} to refer to the global `window` object. For example, if you want to call `alert()`, which is defined on `window`, in an expression must use `$window.alert()`. This is done intentionally to prevent accidental access to the global state (a common source of subtle bugs). @@ -162,7 +162,7 @@ of filters like this: name | uppercase The expression evaluator simply passes the value of name to {@link -api/angular.module.ng.$filter.uppercase `uppercase`} filter. +api/ng.filter:uppercase `uppercase`} filter. Chain filters using this syntax: |