From 9858f8aa61705ea87a36ab34ae4774da4b5180bb Mon Sep 17 00:00:00 2001
From: niallobrien <me@niallobrien.me>
Date: Wed, 27 Jun 2012 14:19:21 +0200
Subject: [PATCH] Added examples for using $errors in views.

---
 laravel/documentation/validation.md | 21 ++++++++++++++++++++-
 1 file changed, 20 insertions(+), 1 deletion(-)

diff --git a/laravel/documentation/validation.md b/laravel/documentation/validation.md
index 4da4683c..690bd54e 100644
--- a/laravel/documentation/validation.md
+++ b/laravel/documentation/validation.md
@@ -304,7 +304,26 @@ ## Validation Walkthrough
 
 Great! So, we have two simple registration routes. One to handle displaying the form, and one to handle the posting of the form. In the POST route, we run some validation over the input. If the validation fails, we redirect back to the registration form and flash the validation errors to the session so they will be available for us to display.
 
-**But, notice we are not explicitly binding the errors to the view in our GET route**. However, an errors variable will still be available in the view. Laravel intelligently determines if errors exist in the session, and if they do, binds them to the view for you. If no errors exist in the session, an empty message container will still be bound to the view. In your views, this allows you to always assume you have a message container available via the errors variable. We love making your life easier.
+**But, notice we are not explicitly binding the errors to the view in our GET route**. However, an errors variable ($errors) will still be available in the view. Laravel intelligently determines if errors exist in the session, and if they do, binds them to the view for you. If no errors exist in the session, an empty message container will still be bound to the view. In your views, this allows you to always assume you have a message container available via the errors variable. We love making your life easier.
+
+For example, if email address validation failed, we can look for 'email' within the $errors session var.
+
+	$errors->has('email')
+
+Using Blade, we can then conditionally add error messages to our view.
+
+	{{ $errors->has('email') ? 'Invalid Email Address' : 'Condition is false. Can be left blank' }}
+
+This will also work great when we need to conditionally add classes when using something like Twitter Bootstrap.
+For example, if the email address failed validation, we may want to add the "error" class from Bootstrap to our *div class="control-group"* statement.
+
+	<div class="control-group {{ $errors->has('email') ? 'error' : '' }}">
+	
+When the validation fails, our rendered view will have the appended *error* class.
+
+	<div class="control-group error">
+	
+
 
 <a name="custom-error-messages"></a>
 ## Custom Error Messages