From b36bb974518cd11dbd43ec6ba1e2b95ed02a07b8 Mon Sep 17 00:00:00 2001
From: poshest <joshoooaaah@gmail.com>
Date: Tue, 18 Mar 2014 00:02:15 +0100
Subject: [PATCH] Update nonassign.ngdoc

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, because this was my error, and the documentation led me to try every permutation of attribute values on <my-directive>1, and completely missed the fact that <my-directive>2 in my code didn't have ANY attribute.  If my proposed edit had been there, I might have found my problem earlier.
---
 docs/content/error/$compile/nonassign.ngdoc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/content/error/$compile/nonassign.ngdoc b/docs/content/error/$compile/nonassign.ngdoc
index 3a7d996b647a..7486ba707985 100644
--- a/docs/content/error/$compile/nonassign.ngdoc
+++ b/docs/content/error/$compile/nonassign.ngdoc
@@ -30,6 +30,9 @@ Following are invalid uses of this directive:
 
 <!-- ERROR because `myFn()=localValue` is an invalid statement -->
 <my-directive bind="myFn()">
+
+<!-- ERROR because attribute bind wasn't provided -->
+<my-directive>
 ```