From 33e1bdc543bcb7875dcc004d487333393670ed2d Mon Sep 17 00:00:00 2001
From: Peter Bacon Darwin
Date: Sun, 16 Feb 2014 22:02:31 +0000
Subject: chore(errors): rename folders to match namespaces

---
 docs/content/error/compile/nonassign.ngdoc | 41 ------------------------------
 1 file changed, 41 deletions(-)
 delete mode 100644 docs/content/error/compile/nonassign.ngdoc

(limited to 'docs/content/error/compile/nonassign.ngdoc')

diff --git a/docs/content/error/compile/nonassign.ngdoc b/docs/content/error/compile/nonassign.ngdoc
deleted file mode 100644
index 3a7d996b..00000000
--- a/docs/content/error/compile/nonassign.ngdoc
+++ /dev/null
@@ -1,41 +0,0 @@
-@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()">
-```
-
-
-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']">
-```
-
-- 
cgit v1.2.3