aboutsummaryrefslogtreecommitdiffstats
path: root/docs/content/error/compile/nonassign.ngdoc
diff options
context:
space:
mode:
authorBrian Ford2013-10-23 14:04:47 -0700
committerBrian Ford2013-10-23 14:17:27 -0700
commite69c2872939cda30f13a1a8390bbc61662c12d9a (patch)
tree20b3bb618dae4b282b51097cd5defcba83c12003 /docs/content/error/compile/nonassign.ngdoc
parent32ab648c79b4783f1cc2491919b659d17004356c (diff)
downloadangular.js-e69c2872939cda30f13a1a8390bbc61662c12d9a.tar.bz2
docs(guide/directive,guide/compiler,): drastically improve
Diffstat (limited to 'docs/content/error/compile/nonassign.ngdoc')
-rw-r--r--docs/content/error/compile/nonassign.ngdoc4
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/content/error/compile/nonassign.ngdoc b/docs/content/error/compile/nonassign.ngdoc
index 9f78ed3f..3870c2ed 100644
--- a/docs/content/error/compile/nonassign.ngdoc
+++ b/docs/content/error/compile/nonassign.ngdoc
@@ -3,7 +3,9 @@
@fullName Non-Assignable Expression
@description
-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#writing-directives_directive-definition-object directive definition}) but the directive is used with an expression that is not-assignable.
+This error occurs when a directive defines an isolate scope property
+(using the `=` mode in the {@link api/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.