There are two main methods for request verification in Laravel: controller verification and form request classes. 1. The validate() method in the controller is suitable for simple scenarios, directly passing rules and automatically returning errors; 2. The Form Request class is suitable for complex or reusable scenarios, creating classes through Artisan and defining rules in rules() to achieve code decoupling and reusing; 3. You can customize error prompts through messages() to improve user experience; 4. Defining field alias through attributes() to make error messages more friendly; the two methods have their advantages and disadvantages, and the appropriate solution should be selected according to project needs.

Request Validation is actually quite straightforward, especially after using it a few times, you will find that the routine is very clear. You can choose to verify directly in the controller, or use a special form request class (Form Request). The key is how to choose the appropriate method to handle different scenarios.

Use validate method in the controller

The most common and easiest way is to use the validate() function in the controller method. This method accepts request data and verification rules, and will automatically return an error message if verification fails.

For example, when you are processing a user registration request, you can write this:

 public function store(Request $request)
{
    $validated = $request->validate([
        'name' => 'required|string|max:255',
        'email' => 'required|email|unique:users',
        'password' => 'required|min:6',
    ]);

    // Continue to execute logic after verification}

This approach is suitable for simple form submissions or API requests. Its advantages are fast and intuitive, and no additional file creation is required. But if your verification logic becomes complicated, or if you have to use the same rules in multiple places, it is not recommended.

Use the Form Request class for more flexible verification

Custom Form Request comes in handy when your verification logic starts to grow, or you want to reuse certain rules. You can use the Artisan command to generate one:

 php artisan make:request StoreUserRequest

Then open the generated app/Http/Requests/StoreUserRequest.php file and write the verification rules in rules() method:

 public function rules()
{
    Return [
        'name' => 'required|string|max:255',
        'email' => 'required|email|unique:users',
        'password' => 'required|min:6',
    ];
}

Then introduce it directly in the controller and use it:

 use App\Http\Requests\StoreUserRequest;

public function store(StoreUserRequest $request)
{
    // Enter here to indicate that it has passed the verification}

There are several benefits to doing this:

• Remove verification logic from the controller and keep the code neat.
• The same request class can be reused.
• Support authorization logic (you can add authorize() method to determine whether the user has permission to submit).

Custom error prompts and field alias

The default error prompt may not be friendly enough, you can customize the prompt by adding messages() method:

 public function messages()
{
    Return [
        'name.required' => 'Name is a required item',
        'email.email' => 'Please enter the correct email format',
    ];
}

In addition, you can also use attributes() method to give the field an alias to make the error message easier to read:

 public function attributes()
{
    Return [
        'name' => 'name',
        'email' => 'email address',
    ];
}

This way, the prompts users see are more natural.

Basically that's it. Laravel's verification mechanism is designed very practically, and suitable solutions can be found in both simple scenarios and complex businesses. The key is to choose the appropriate method based on the project size and needs, use controller to verify small functions, and use Form Request for large forms or multiplexing scenarios.

The above is the detailed content of How to perform Request Validation in Laravel?. For more information, please follow other related articles on the PHP Chinese website!