Custom error messages in Laravel - Mini Project: Build & Apply

Custom error messages in Laravel validation

📖 Scenario: You are building a simple Laravel form to collect user registration data. You want to make sure users get clear, friendly error messages if they enter invalid data.

🎯 Goal: Create a Laravel validation setup that uses custom error messages for the name and email fields.

📋 What You'll Learn

Create a validation rules array with name required and minimum 3 characters

Add a validation rule for email to be required and a valid email

Create a custom error messages array with specific messages for name.required, name.min, and email.email

Use the validate method with rules and custom messages in a controller method

💡 Why This Matters

🌍 Real World

Custom error messages help users understand exactly what is wrong with their input, improving user experience in web forms.

💼 Career

Knowing how to customize validation messages is a common task for Laravel developers building user-friendly applications.

1

Set up validation rules array

Create a variable called $rules as an array with these exact entries: 'name' => 'required|min:3' and 'email' => 'required|email'.

Laravel

<?php

namespace App\Http\Controllers;

use Illuminate\Http\Request;

class RegisterController extends Controller
{
    public function store(Request $request)
    {
        // Create the validation rules array
        // Your code here
    }
}

Hint

Use an associative array with keys 'name' and 'email' and string values for rules.

2

Add custom error messages array

Create a variable called $messages as an array with these exact entries: 'name.required' => 'Please enter your name.', 'name.min' => 'Name must be at least 3 characters.', and 'email.email' => 'Please enter a valid email address.'.

Laravel

 'required|min:3',
            'email' => 'required|email',
        ];
        // Create the custom error messages array
        // Your code here
    }
}

Hint

Use an associative array with keys matching the rule names and values as the custom messages.

3

Apply validation with rules and messages

Use $request->validate() method with the variables $rules and $messages as arguments inside the store method.

Laravel

 'required|min:3',
            'email' => 'required|email',
        ];

        $messages = [
            'name.required' => 'Please enter your name.',
            'name.min' => 'Name must be at least 3 characters.',
            'email.email' => 'Please enter a valid email address.',
        ];
        // Validate the request with rules and messages
        // Your code here
    }
}

Hint

Call $request->validate($rules, $messages); to apply validation with custom messages.

4

Complete the controller method

Add a return statement that redirects back with input using return redirect()->back()->withInput(); after validation to complete the method.

Laravel

 'required|min:3',
            'email' => 'required|email',
        ];

        $messages = [
            'name.required' => 'Please enter your name.',
            'name.min' => 'Name must be at least 3 characters.',
            'email.email' => 'Please enter a valid email address.',
        ];

        $request->validate($rules, $messages);
        // Add redirect back with input
        // Your code here
    }
}

Hint

Use return redirect()->back()->withInput(); to send the user back to the form with their entered data.

Practice

1. What is the main purpose of defining custom error messages in Laravel validation?

easy

A. To speed up the validation process

B. To disable validation rules temporarily

C. To automatically fix user input errors

D. To show user-friendly messages instead of default error texts

Solution

1. Step 1: Understand default validation behavior

   Laravel shows default error messages when validation fails, which may be generic or unclear.

2. Step 2: Purpose of custom messages

   Custom error messages replace these defaults with clearer, friendlier texts to help users understand mistakes.

3. Final Answer:

   To show user-friendly messages instead of default error texts -> Option D

4. Quick Check:

   Custom messages improve clarity = A [OK]

Hint: Custom messages improve user clarity, not validation logic [OK]

Common Mistakes:

• Thinking custom messages change validation rules
• Believing they fix input automatically
• Confusing speed with message customization

2. Which syntax correctly defines a custom error message for the 'email' field's 'required' rule in a Laravel Form Request?

easy

A. 'email:required' => 'Email is mandatory.'

B. 'required.email' => 'Email is mandatory.'

C. 'email.required' => 'Email is mandatory.'

D. 'required-email' => 'Email is mandatory.'

Solution

1. Step 1: Recall Laravel message key format

   Custom messages use 'field.rule' as the key, e.g., 'email.required'.

2. Step 2: Match correct syntax

   'email.required' => 'Email is mandatory.' uses 'email.required' correctly; others misuse order or separators.

3. Final Answer:

   'email.required' => 'Email is mandatory.' -> Option C

4. Quick Check:

   Message keys = 'field.rule' format [OK]

Hint: Use 'field.rule' format for custom messages [OK]

Common Mistakes:

• Swapping field and rule order
• Using colons or dashes instead of dot
• Missing quotes around keys

3. Given this Laravel validation snippet in a Form Request class:

public function messages() {
    return [
        'name.required' => 'Name cannot be empty.',
        'email.email' => 'Please enter a valid email address.'
    ];
}

What message will be shown if the user submits the form with an empty 'name' and an invalid 'email'?

medium

A. Name cannot be empty.\nPlease enter a valid email address.

B. The name field is required.\nThe email must be a valid email address.

C. Name cannot be empty.\nThe email must be a valid email address.

D. The name field is required.\nPlease enter a valid email address.

Solution

1. Step 1: Identify custom messages for failed rules

   The 'name.required' and 'email.email' rules have custom messages defined.

2. Step 2: Match messages to errors

   Empty 'name' triggers 'name.required' message: 'Name cannot be empty.' Invalid 'email' triggers 'email.email' message: 'Please enter a valid email address.'

3. Final Answer:

   Name cannot be empty.\nPlease enter a valid email address. -> Option A

4. Quick Check:

   Custom messages shown for failed rules = B [OK]

Hint: Custom messages override defaults for matching rules [OK]

Common Mistakes:

• Assuming default messages show despite custom ones
• Mixing messages from different rules
• Ignoring line breaks in output

4. You wrote this custom message in your Form Request:

public function messages() {
    return [
        'password.min' => 'Password must be at least 8 characters.'
    ];
}

But when the password is too short, the default Laravel message shows instead. What is the likely cause?

medium

A. The messages() method is missing the 'required' message for password

B. The validation rule might be 'min' but the field name is incorrect or missing

C. The key 'password.min' is correct; the issue is elsewhere

D. The validation rule is named 'min:8', so the key should be 'password.min:8'

Solution

1. Step 1: Check message key correctness

   'password.min' is the correct key format for the min rule on password field.

2. Step 2: Consider validation rule and field name

   If the validation rule is applied to a different field or the field name is misspelled, the message won't match and default shows.

3. Final Answer:

   The validation rule might be 'min' but the field name is incorrect or missing -> Option B

4. Quick Check:

   Message keys must match exact field and rule names [OK]

Hint: Ensure message keys match exact field and rule names [OK]

Common Mistakes:

• Adding parameters like ':8' in message keys
• Missing validation rule on the field
• Typos in field names

5. You want to show a custom error message for the 'age' field only when it fails the 'between:18,65' rule. How should you define this message in your Form Request's messages() method?

hard

A. 'age.between' => 'Age must be between 18 and 65 years.'

B. 'age.between:18,65' => 'Age must be between 18 and 65 years.'

C. 'between.age' => 'Age must be between 18 and 65 years.'

D. 'age.between_rule' => 'Age must be between 18 and 65 years.'

Solution

1. Step 1: Recall message key format for rules with parameters

   Laravel uses 'field.rule' keys without parameters for custom messages, even if the rule has parameters.

2. Step 2: Identify correct key for 'between' rule on 'age'

   The key is 'age.between', not including ':18,65' or other suffixes.

3. Final Answer:

   'age.between' => 'Age must be between 18 and 65 years.' -> Option A

4. Quick Check:

   Use 'field.rule' keys without parameters for messages [OK]

Hint: Ignore parameters in message keys; use 'field.rule' only [OK]

Common Mistakes:

• Including parameters like ':18,65' in keys
• Swapping field and rule order
• Using invalid suffixes like '_rule'