Hopiu/angular.js
1
0
Fork 0
mirror of https://github.com/Hopiu/angular.js.git synced 2026-05-16 18:51:06 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs(guide/directive): fix names in scope '='; easier to grok

Browse source
This commit is contained in:
Tim Macfarlane 2012-11-07 09:23:20 +00:00 committed by Igor Minar
parent 60acba3840
commit 27cee7db0a
1 changed files with 11 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
docs/content/guide/directive.ngdoc
View file

@ -321,24 +321,26 @@ compiler}. The attributes are:
derived from the parent scope. These local properties are useful for aliasing values for derived from the parent scope. These local properties are useful for aliasing values for
templates. Locals definition is a hash of local scope property to its source: templates. Locals definition is a hash of local scope property to its source:
* `@` or `@attr` - bind a local scope property to the DOM attribute. The result is always a * `@` or `@attr` - bind a local scope property to the value of DOM attribute. The result is
string since DOM attributes are strings. If no `attr` name is specified then the local name always a string since DOM attributes are strings. If no `attr` name is specified then the
and attribute name are same. Given `<widget my-attr="hello {{name}}">` and widget definition attribute name is assumed to be the same as the local name.
Given `<widget my-attr="hello {{name}}">` and widget definition
of `scope: { localName:'@myAttr' }`, then widget scope property `localName` will reflect of `scope: { localName:'@myAttr' }`, then widget scope property `localName` will reflect
the interpolated value of `hello {{name}}`. As the `name` attribute changes so will the the interpolated value of `hello {{name}}`. As the `name` attribute changes so will the
`localName` property on the widget scope. The `name` is read from the parent scope (not `localName` property on the widget scope. The `name` is read from the parent scope (not
component scope). component scope).
* `=` or `=expression` - set up bi-directional binding between a local scope property and the * `=` or `=attr` - set up bi-directional binding between a local scope property and the
parent scope property. If no `attr` name is specified then the local name and attribute parent scope property of name defined via the value of the `attr` attribute. If no `attr`
name are same. Given `<widget my-attr="parentModel">` and widget definition of name is specified then the attribute name is assumed to be the same as the local name.
`scope: { localModel:'=myAttr' }`, then widget scope property `localName` will reflect the Given `<widget my-attr="parentModel">` and widget definition of
`scope: { localModel:'=myAttr' }`, then widget scope property `localModel` will reflect the
value of `parentModel` on the parent scope. Any changes to `parentModel` will be reflected value of `parentModel` on the parent scope. Any changes to `parentModel` will be reflected
in `localModel` and any changes in `localModel` will reflect in `parentModel`. in `localModel` and any changes in `localModel` will reflect in `parentModel`.
* `&` or `&attr` - provides a way to execute an expression in the context of the parent scope. * `&` or `&attr` - provides a way to execute an expression in the context of the parent scope.
If no `attr` name is specified then the local name and attribute name are same. If no `attr` name is specified then the attribute name is assumed to be the same as the
Given `<widget my-attr="count = count + value">` and widget definition of local name. Given `<widget my-attr="count = count + value">` and widget definition of
`scope: { localFn:'&myAttr' }`, then isolate scope property `localFn` will point to `scope: { localFn:'&myAttr' }`, then isolate scope property `localFn` will point to
a function wrapper for the `increment()` expression. Often it's desirable to pass data from a function wrapper for the `increment()` expression. Often it's desirable to pass data from
the isolate scope via an expression and to the parent scope, this can be done by passing a the isolate scope via an expression and to the parent scope, this can be done by passing a