0Showing validation errors helps users know what they need to fix in a form. It makes the app easier and friendlier to use.
@if ($errors->any())
<div class="alert alert-danger">
<ul>
@foreach ($errors->all() as $error)
<li>{{ $error }}</li>
@endforeach
</ul>
</div>
@endif$errors->any() to check if there are any validation errors.$errors->all() to get all error messages as an array.@if ($errors->any())
<div class="error-messages">
<ul>
@foreach ($errors->all() as $error)
<li>{{ $error }}</li>
@endforeach
</ul>
</div>
@endif@error('email') <div class="error">{{ $message }}</div> @enderror
<input type="text" name="username" value="{{ old('username') }}"> @error('username') <span class="text-danger">{{ $message }}</span> @enderror
This example shows a controller method that validates user input for name and email. If validation fails, Laravel automatically redirects back with errors. The Blade view displays errors next to each field and also lists all errors at the bottom.
<?php namespace App\Http\Controllers; use Illuminate\Http\Request; class UserController extends Controller { public function store(Request $request) { $validated = $request->validate([ 'name' => 'required|min:3', 'email' => 'required|email', ]); // Save user or other logic here return redirect()->back()->with('success', 'User saved!'); } } // Blade view snippet (resources/views/user_form.blade.php): /* <form method="POST" action="{{ route('user.store') }}"> @csrf <label for="name">Name:</label> <input type="text" id="name" name="name" value="{{ old('name') }}"> @error('name') <div class="error">{{ $message }}</div> @enderror <label for="email">Email:</label> <input type="email" id="email" name="email" value="{{ old('email') }}"> @error('email') <div class="error">{{ $message }}</div> @enderror <button type="submit">Submit</button> </form> @if ($errors->any()) <div class="alert alert-danger"> <ul> @foreach ($errors->all() as $error) <li>{{ $error }}</li> @endforeach </ul> </div> @endif */
Laravel automatically redirects back with errors if validation fails.
Use old('field') to keep user input after validation fails.
Showing errors near fields helps users fix mistakes faster.
Validation errors tell users what to fix in forms.
Use $errors->any() and $errors->all() to display errors.
Show errors near inputs and optionally as a list for better user experience.
$errors->any() check in a Laravel Blade view?$errors$errors holds validation error messages after form submission.$errors->any()$errors->any() checks for errors [OK]$errors->any() means errors exist [OK]$errors->any() with form submission status$errors->any() to confirm if errors exist before displaying.$errors->all() inside a @foreach to list each error in <li>.$errors->any() + $errors->all() [OK]$errors->any() before looping $errors->all() [OK]$errors->any() and $errors->all() in loops@if($errors->any())@endif@foreach($errors->all() as $error)
- {{ $error }}
@endforeach
@if($errors->any()) condition is true because there are two errors.<ul> with each error in <li>, wrapped by <div class="alert">.@if($errors->all())
@if($errors->all()) condition$errors->all() returns an array, so it can be truthy if errors exist, this is acceptable but less common than $errors->any().@foreach($errors->any() as $error) loop$errors->any() returns a boolean, which cannot be looped. This causes an error.$errors->any() returns boolean, cannot be looped -> Option A$errors->all(), not $errors->any() [OK]$errors->all(), not $errors->any() [OK]$errors->any()$errors->any() and $errors->all()@error('field') to check and display the first error message for that field using $message.<span> with class error is a common pattern for styling.@error('field') for single field error [OK]@error('field') to show first error message [OK]$errors->all('field') which returns array, not string@error directive for single errorsPass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.