There are four main ways to create custom validation rules in Laravel. First, use Rule objects to add complex conditions, such as combining database queries and ignore methods to achieve unique verification; second, encapsulate custom logic in form requests, and reuse and clear structure by rewriting rules() method; third, use closures to write instant rules, suitable for simple judgment scenarios; fourth, create custom rule classes to make the organization clearer and easier for testing and team collaboration. Developers should choose appropriate verification methods based on specific business scenarios to improve code maintainability and development efficiency.
Creating custom validation rules in Laravel is not difficult, the key is to understand the several flexible ways the framework provides. Laravel native validators are already powerful, but some business logic may require you to write custom rules to ensure the accuracy of your data.

Add complex conditions using Rule objects
When your verification logic is a little more complicated, using Rule
objects is a good choice. It is often used for database-related checks, such as determining whether a field is unique under specified conditions.

For example: Suppose you want to verify whether the email address already exists when editing user information, but you don’t want to count the current user’s email address as well:
use Illuminate\Validation\Rule; $request->validate([ 'email' => [ 'required', 'email', Rule::unique('users')->ignore($user->id), ], ]);
This can avoid misjudging duplicate emails by ignoring IDs. You can also chain call the where method to further refine the query conditions.

Encapsulate custom logic in form request
If your verification rules are complicated or if the same logic is used in multiple places, it is recommended to use a custom form request (Form Request) . You can create a form request class through Artisan:
php artisan make:request StorePostRequest
Then rewrite rules()
method in the generated class and add your own logic:
public function rules() { Return [ 'title' => 'required|unique:posts|max:255', 'body' => 'required', ]; }
You can also add custom judgments directly, such as deciding whether to allow posting of articles based on the user role.
Writing instant rules using closures
Sometimes you don't need too complex structures, just want to add a verification logic quickly, and you can use closures:
'title' => [ 'required', function ($attribute, $value, $fail) { if (strtolower($value) === 'admin') { $fail('The '.$attribute.' cannot be "admin".'); } }, ],
This writing method is suitable for simple judgments, but is not suitable for handling too complex logic, otherwise it will make the code difficult to maintain.
Custom Rule Class: A clearer way to organize
For large projects or frequently reused rules, Laravel provides methods to create custom rule classes:
php artisan make:rule ValidUsername
The generated class will have a passes()
method and a message()
method:
class ValidUsername { public function passes($attribute, $value) { return !preg_match('/\s/', $value); } public function message() { return 'Username cannot contain spaces. '; } }
Then use it like this when verifying:
'username' => ['required', new ValidUsername];
This approach is suitable for teamwork and is easier to test and reuse.
In general, Laravel offers a variety of ways to implement custom validation rules, and you can choose the most appropriate way based on the specific scenario. It is not complicated, but the details are easy to ignore: when to use closures, when to abstract them into classes, and how to write efficient rules based on database queries.
The above is the detailed content of Creating Custom Validation Rules in Laravel?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

ToworkeffectivelywithpivottablesinLaravel,firstaccesspivotdatausingwithPivot()orwithTimestamps(),thenupdateentrieswithupdateExistingPivot(),managerelationshipsviadetach()andsync(),andusecustompivotmodelswhenneeded.1.UsewithPivot()toincludespecificcol

Laravelprovidesacleanandflexiblewaytosendnotificationsviamultiplechannelslikeemail,SMS,in-appalerts,andpushnotifications.Youdefinenotificationchannelsinthevia()methodofanotificationclass,andimplementspecificmethodsliketoMail(),toDatabase(),ortoVonage

Dependency injection automatically handles class dependencies through service containers in Laravel without manual new objects. Its core is constructor injection and method injection, such as automatically passing in the Request instance in the controller. Laravel parses dependencies through type prompts and recursively creates the required objects. The binding interface and implementation can be used by the service provider to use the bind method, or singleton to bind a singleton. When using it, you need to ensure type prompts, avoid constructor complications, use context bindings with caution, and understand automatic parsing rules. Mastering these can improve code flexibility and maintenance.

Laravel performance optimization can improve application efficiency through four core directions. 1. Use the cache mechanism to reduce duplicate queries, store infrequently changing data through Cache::remember() and other methods to reduce database access frequency; 2. Optimize database from the model to query statements, avoid N 1 queries, specifying field queries, adding indexes, paging processing and reading and writing separation, and reduce bottlenecks; 3. Use time-consuming operations such as email sending and file exporting to queue asynchronous processing, use Supervisor to manage workers and set up retry mechanisms; 4. Use middleware and service providers reasonably to avoid complex logic and unnecessary initialization code, and delay loading of services to improve startup efficiency.

Methods to manage database state in Laravel tests include using RefreshDatabase, selective seeding of data, careful use of transactions, and manual cleaning if necessary. 1. Use RefreshDatabasetrait to automatically migrate the database structure to ensure that each test is based on a clean database; 2. Use specific seeds to fill the necessary data and generate dynamic data in combination with the model factory; 3. Use DatabaseTransactionstrait to roll back the test changes, but pay attention to its limitations; 4. Manually truncate the table or reseed the database when it cannot be automatically cleaned. These methods are flexibly selected according to the type of test and environment to ensure the reliability and efficiency of the test.

LaravelSanctum is suitable for simple, lightweight API certifications such as SPA or mobile applications, while Passport is suitable for scenarios where full OAuth2 functionality is required. 1. Sanctum provides token-based authentication, suitable for first-party clients; 2. Passport supports complex processes such as authorization codes and client credentials, suitable for third-party developers to access; 3. Sanctum installation and configuration are simpler and maintenance costs are low; 4. Passport functions are comprehensive but configuration is complex, suitable for platforms that require fine permission control. When selecting, you should determine whether the OAuth2 feature is required based on the project requirements.

Laravel simplifies database transaction processing with built-in support. 1. Use the DB::transaction() method to automatically commit or rollback operations to ensure data integrity; 2. Support nested transactions and implement them through savepoints, but it is usually recommended to use a single transaction wrapper to avoid complexity; 3. Provide manual control methods such as beginTransaction(), commit() and rollBack(), suitable for scenarios that require more flexible processing; 4. Best practices include keeping transactions short, only using them when necessary, testing failures, and recording rollback information. Rationally choosing transaction management methods can help improve application reliability and performance.

The core of handling HTTP requests and responses in Laravel is to master the acquisition of request data, response return and file upload. 1. When receiving request data, you can inject the Request instance through type prompts and use input() or magic methods to obtain fields, and combine validate() or form request classes for verification; 2. Return response supports strings, views, JSON, responses with status codes and headers and redirect operations; 3. When processing file uploads, you need to use the file() method and store() to store files. Before uploading, you should verify the file type and size, and the storage path can be saved to the database.
