Validate method on request in Laravel - Mini Project: Build & Apply

Validate method on request

📖 Scenario: You are building a simple Laravel web application where users submit a form with their name and email. You want to make sure the data is valid before saving it.

🎯 Goal: Create a Laravel controller method that uses the validate method on the request to check that the name is required and at least 3 characters long, and the email is required and a valid email address.

📋 What You'll Learn

Create a controller method named store that accepts a Request object

Use the validate method on the $request to validate name and email

The name field must be required and have a minimum length of 3

The email field must be required and be a valid email

Return a simple success message after validation

💡 Why This Matters

🌍 Real World

Validating user input is essential in web applications to prevent bad data and security issues.

💼 Career

Laravel developers frequently use the validate method on requests to enforce data rules before processing.

1

Create the controller method with Request parameter

Create a public method called store inside a controller that accepts a Request parameter named $request.

Laravel

<?php

namespace App\Http\Controllers;

use Illuminate\Http\Request;

class UserController extends Controller
{
    // Create the store method with Request parameter
    // Your code here
}

Hint

Remember to declare the method as public and accept Request $request as the parameter.

2

Add validation rules using the validate method

Inside the store method, use $request->validate() to validate that name is required and minimum 3 characters, and email is required and a valid email.

Laravel

validate() with rules for name and email
        // Your code here
    }
}

Hint

Use an array inside validate() with keys 'name' and 'email' and their validation rules.

3

Add a success response after validation

After the $request->validate() call, return a string 'Validation passed!' from the store method.

Laravel

validate([
            'name' => ['required', 'min:3'],
            'email' => ['required', 'email'],
        ]);
        // Return 'Validation passed!' string
        // Your code here
    }
}

Hint

Simply return the string after validation to confirm success.

4

Complete the controller with namespace and use statements

Ensure the controller file starts with the correct namespace App\Http\Controllers; and includes use Illuminate\Http\Request; at the top.

Laravel

validate([
            'name' => ['required', 'min:3'],
            'email' => ['required', 'email'],
        ]);

        return 'Validation passed!';
    }
}

Hint

The namespace and use statements must be at the top of the file before the class.

Practice

1. What does the validate method on a Laravel request do?

easy

A. It saves the user input directly to the database.

B. It checks if the user input meets specified rules and returns errors if not.

C. It formats the user input into JSON automatically.

D. It sends an email notification when input is received.

Solution

1. Step 1: Understand the purpose of validate

   The validate method is designed to check user input against rules.

2. Step 2: Recognize Laravel's automatic error handling

   If input does not meet rules, Laravel sends errors back automatically without saving or formatting data.

3. Final Answer:

   It checks if the user input meets specified rules and returns errors if not. -> Option B

4. Quick Check:

   Validation = Input check and error return [OK]

Hint: Validate means check input rules and return errors [OK]

Common Mistakes:

• Thinking validate saves data
• Confusing validate with formatting methods
• Assuming validate sends emails

2. Which of the following is the correct syntax to validate a request with a required email field in Laravel?

easy

A. $request->validate(['email' => required, 'email']);

B. $request->validate('email' => 'required|email');

C. $request->validate(['email' => 'required|email']);

D. $request->validate(['email' => required|email]);

Solution

1. Step 1: Check the array syntax for rules

   Rules must be passed as an associative array with field names as keys and rule strings as values.

2. Step 2: Confirm correct string format for rules

   Rules are strings separated by pipe characters, e.g., 'required|email'.

3. Final Answer:

   $request->validate(['email' => 'required|email']); -> Option C

4. Quick Check:

   Array with string rules = correct syntax [OK]

Hint: Use array with field => 'rules' string [OK]

Common Mistakes:

• Missing array brackets
• Not quoting the rules string
• Separating rules incorrectly

3. Given this code snippet, what happens if the user submits an empty 'name' field?

$validated = $request->validate([
    'name' => 'required|string',
    'age' => 'nullable|integer'
]);

medium

A. The validation fails and Laravel redirects back with an error for 'name'.

B. The validation passes and $validated contains 'name' as an empty string.

C. The validation fails but no error message is shown.

D. The validation passes and 'age' is set to zero automatically.

Solution

1. Step 1: Understand the 'required' rule on 'name'

   The 'required' rule means the 'name' field must be present and not empty.

2. Step 2: Analyze empty input for 'name'

   An empty 'name' fails the 'required' rule, so validation fails and Laravel redirects back with errors.

3. Final Answer:

   The validation fails and Laravel redirects back with an error for 'name'. -> Option A

4. Quick Check:

   Empty required field = validation fail [OK]

Hint: Required means field cannot be empty [OK]

Common Mistakes:

• Assuming empty string passes 'required'
• Thinking validation passes silently
• Confusing 'nullable' with 'required'

4. Identify the error in this validation code:

return $request->validate([
    'email' => 'required|email',
    'password' => required|min:8
]);

medium

A. The validate method should not return anything.

B. The 'email' rule is missing for the 'email' field.

C. The array brackets are missing around the rules.

D. The 'required' rule for 'password' is not quoted as a string.

Solution

1. Step 1: Check the syntax of rules for each field

   Rules must be strings inside quotes, e.g., 'required|min:8'.

2. Step 2: Identify missing quotes in 'password' rules

   The 'password' rules are not quoted, causing a syntax error.

3. Final Answer:

   The 'required' rule for 'password' is not quoted as a string. -> Option D

4. Quick Check:

   Rules must be strings in quotes [OK]

Hint: Always quote validation rules as strings [OK]

Common Mistakes:

• Forgetting quotes around rules
• Misplacing array brackets
• Thinking validate returns void always

5. You want to validate a request so that the 'username' is required, must be a string, and unique in the 'users' table, but only if the user is creating a new record (not updating). Which validation rule is correct?

hard

A. $request->validate(['username' => 'required|string|unique:users']);

B. $request->validate(['username' => 'required|string|unique']);

C. $request->validate(['username' => 'required|string|unique:users,username,' . $user->id]);

D. $request->validate(['username' => 'required|string|unique:users.username']);

Solution

1. Step 1: Understand the unique rule for new records

   For new records, the unique rule is simply 'unique:table' or 'unique:table,column'.

2. Step 2: Identify the rule that applies only for new records

   $request->validate(['username' => 'required|string|unique:users']); uses 'unique:users' which checks uniqueness in the users table without exceptions.

3. Step 3: Eliminate incorrect options

   A omits the table name, C is for updates (ignores current user ID), D uses invalid syntax 'unique:users.username' (dot instead of comma).

4. Final Answer:

   $request->validate(['username' => 'required|string|unique:users']); -> Option A

5. Quick Check:

   Unique rule with table name only = new record check [OK]

Hint: Use 'unique:table' for new record uniqueness [OK]

Common Mistakes:

• Using update syntax for new records
• Omitting table name in unique rule
• Confusing unique rule format