mirror of
https://github.com/zhigang1992/angular.js.git
synced 2026-04-09 17:10:34 +08:00
c9fbb472b7
It might seem obvious that if you don't supply "bind" attribute in this case, you'll get an error, but I feel this is worth adding to the doc. Closes #6725
45 lines
1.2 KiB
Plaintext
45 lines
1.2 KiB
Plaintext
@ngdoc error
|
|
@name $compile:nonassign
|
|
@fullName Non-Assignable Expression
|
|
@description
|
|
|
|
This error occurs when a directive defines an isolate scope property
|
|
(using the `=` mode in the {@link ng.$compile#description_comprehensive-directive-api_directive-definition-object
|
|
`scope` option} of a directive definition) but the directive is used with an expression that is not-assignable.
|
|
|
|
In order for the two-way data-binding to work, it must be possible to write new values back into the path defined with the expression.
|
|
|
|
For example, given a directive:
|
|
|
|
```
|
|
myModule.directive('myDirective', function factory() {
|
|
return {
|
|
...
|
|
scope: {
|
|
'bind': '=localValue'
|
|
}
|
|
...
|
|
}
|
|
});
|
|
```
|
|
|
|
Following are invalid uses of this directive:
|
|
```
|
|
<!-- ERROR because `1+2=localValue` is an invalid statement -->
|
|
<my-directive bind="1+2">
|
|
|
|
<!-- ERROR because `myFn()=localValue` is an invalid statement -->
|
|
<my-directive bind="myFn()">
|
|
|
|
<!-- ERROR because attribute bind wasn't provided -->
|
|
<my-directive>
|
|
```
|
|
|
|
|
|
To resolve this error, always use path expressions with scope properties that are two-way data-bound:
|
|
```
|
|
<my-directive bind="some.property">
|
|
<my-directive bind="some[3]['property']">
|
|
```
|
|
|