You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
This error occurs when a directive defines an isolate scope property that support two-way data-binding (using the `=` mode in the {@link guide/directive#directivedefinitionobject directive definition}) but the directive is used with an expression that is not-assignable.
7
+
8
+
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.
9
+
10
+
For example, given a directive:
11
+
12
+
```
13
+
myModule.directive('myDirective', function factory() {
14
+
return {
15
+
...
16
+
scope: {
17
+
'bind': '=localValue'
18
+
}
19
+
...
20
+
}
21
+
});
22
+
```
23
+
24
+
Following are invalid uses of this directive:
25
+
```
26
+
<my-directive bind="1+2"> <!-- ERROR because `1+2=localValue` is an invalid statement -->
27
+
<my-directive bind="myFn()"> <!-- ERROR because `myFn()=localValue` is an invalid statement -->
28
+
```
29
+
30
+
31
+
To resolve this error, always use path expressions with scope properties that are two-way data-bound:
0 commit comments