Trong bài này mình sẽ giới thiệu với mọi người về magic methods trong PHP là gì và các magic methods hay dùng trong PHP.
Nội dung chính Show
- 1, Magic methods là gì.
- 2, Ưu nhược điểm của magic methods.
- Ưu điểm
- Nhược điểm
- 3, Các magic method trong PHP.
- 3, Lời kết.
1, Magic methods là gì.
-Magic methods là các phương thức đặc biệt được tạo ra nhằm giải quyết các vấn đề về sự kiện trong chương trình [cụ thể là với class], và đối với PHP cũng thế.
-Từ đầu series đến giờ thực ra các bạn cũng đã được giới thiệu qua về magic methods rồi, phương thức khởi tạo và phương thức hủy trong bài số 6 chính là magic methods.
2, Ưu nhược điểm của magic methods.
-Bất kì một cái gì đó đều có ưu và nhược điểm cả [không có gì là hoàn hảo].
Ưu điểm
-Từ khái niệm trên thì các bạn chắc cũng có thể nhận ra các ưu điểm của nó rồi chứ? nó gồm có các ưu điểm như sau:
- Giúp cho chúng ta tùy biến được các hành vi.
- Nó giúp cho chúng ta có thể khởi tạo một đối tượng theo cách mình muốn.
Nhược điểm
- Một magic methods có tốc độ chậm hơn các phương thức bình thường.
3, Các magic method trong PHP.
-Trong PHP có hỗ trợ chúng ta 15 magic method với từng chức năng khác nhau:
+ __construct[]
: gọi khi khởi tạo đối tượng.
+ __destruct[]
: goij khi hủy đối tượng.
+ __set[]
: gọi khi ta truyền dữ liệu cho một thuộc tính không được phép truy cập.
+ __get[]
: khi đọc dữ liệu từ một thuộc tính không được phép truy cập.
+ __isset[]
: được gọi khi gọi hàm isset[]
hoặc empty[]
trên một thuộc tính không được phép truy cập.
+ __unset[]
: được gọi khi hàm unset[]
được sử dụng trong một thuộc tính không được phép truy cập.
+ __call[]
:được gọi khi ta gọi một phương thức không được phép truy cập trong phạm vi của một đối tượng.
+ __destruct[]
0: được kích hoạt khi ta gọi một phương thức không được phép truy cập trong phạm vi của một phương thức tĩnh.
+ __destruct[]
1: phương thức này giúp class chỉ định xem sẽ in ra cái gì khi nó được dùng.
+ __destruct[]
2:phương thức này được gọi khi một lệnh cố gắng gọi một đối tượng như một hàm.
+ __destruct[]
3: được gọi khi __destruct[]
4 một đối tượng.
+ __destruct[]
5: được gọi khi __destruct[]
6 đối tượng.
+ __destruct[]
7:
+ __destruct[]
8: được sử dụng khi chúng ta clone một object.
+ __destruct[]
9: được gọi khi chúng ta sử dụng hàm __set[]
0.
- Hiện tại thì trên blog của mình đã có đầy đủ các bài hướng dẫn về từng magic methods, các bạn có thể tham khảo thêm ở đây.
3, Lời kết.
-Qua bài này mình đã nêu ra được khai niệm của magic methods và danh sách các magic methods trong PHP rồi, nhưng hiện tại thì mình chưa có bài viết nào hướng dẫn cụ thể về cách sử dụng của từng hàm[ sẽ viết sau] nên các bạn chịu khó đọc tài liệu tiếng anh nhé.
Laravel provides several different approaches to validate your application's incoming data. It is most common to use the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
20 method available on all incoming HTTP requests. However, we will discuss other approaches to validation as well.Laravel includes a wide variety of convenient validation rules that you may apply to data, even providing the ability to validate if values are unique in a given database table. We'll cover each of these validation rules in detail so that you are familiar with all of Laravel's validation features.
Validation Quickstart
To learn about Laravel's powerful validation features, let's look at a complete example of validating a form and displaying the error messages back to the user. By reading this high-level overview, you'll be able to gain a good general understanding of how to validate incoming request data using Laravel:
Defining The Routes
First, let's assume we have the following routes defined in our
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
21 file:use App\Http\Controllers\PostController;
Route::get['/post/create', [PostController::class, 'create']];
Route::post['/post', [PostController::class, 'store']];
The
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
22 route will display a form for the user to create a new blog post, while the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
23 route will store the new blog post in the database.Creating The Controller
Next, let's take a look at a simple controller that handles incoming requests to these routes. We'll leave the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
24 method empty for now:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
Writing The Validation Logic
Now we are ready to fill in our
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
24 method with the logic to validate the new blog post. To do this, we will use the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
20 method provided by the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
27 object. If the validation rules pass, your code will keep executing normally; however, if validation fails, an namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
28 exception will be thrown and the proper error response will automatically be sent back to the user.If validation fails during a traditional HTTP request, a redirect response to the previous URL will be generated. If the incoming request is an XHR request, a JSON response containing the validation error messages will be returned.
To get a better understanding of the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
20 method, let's jump back into the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
24 method: * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
As you can see, the validation rules are passed into the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
20 method. Don't worry - all available validation rules are documented. Again, if the validation fails, the proper response will automatically be generated. If the validation passes, our controller will continue executing normally.Alternatively, validation rules may be specified as arrays of rules instead of a single
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
32 delimited string:$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
In addition, you may use the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
33 method to validate a request and store any error messages within a named error bag:$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
Stopping On First Validation Failure
Sometimes you may wish to stop running validation rules on an attribute after the first validation failure. To do so, assign the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
34 rule to the attribute: 'title' => 'bail|required|unique:posts|max:255',
In this example, if the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
35 rule on the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
36 attribute fails, the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
37 rule will not be checked. Rules will be validated in the order they are assigned.A Note On Nested Attributes
If the incoming HTTP request contains "nested" field data, you may specify these fields in your validation rules using "dot" syntax:
'title' => 'required|unique:posts|max:255',
'author.name' => 'required',
'author.description' => 'required',
On the other hand, if your field name contains a literal period, you can explicitly prevent this from being interpreted as "dot" syntax by escaping the period with a backslash:
'title' => 'required|unique:posts|max:255',
Displaying The Validation Errors
So, what if the incoming request fields do not pass the given validation rules? As mentioned previously, Laravel will automatically redirect the user back to their previous location. In addition, all of the validation errors and request input will automatically be flashed to the session.
An
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
38 variable is shared with all of your application's views by the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
39 middleware, which is provided by the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
40 middleware group. When this middleware is applied an namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
38 variable will always be available in your views, allowing you to conveniently assume the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
38 variable is always defined and can be safely used. The namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
38 variable will be an instance of namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
44. For more information on working with this object, check out its documentation.So, in our example, the user will be redirected to our controller's
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
45 method when validation fails, allowing us to display the error messages in the view:
@foreach [$errors->all[] as $error]
Customizing The Error Messages
Laravel's built-in validation rules each have an error message that is located in your application's
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
46 file. Within this file, you will find a translation entry for each validation rule. You are free to change or modify these messages based on the needs of your application.In addition, you may copy this file to another translation language directory to translate the messages for your application's language. To learn more about Laravel localization, check out the complete localization documentation.
XHR Requests & Validation
In this example, we used a traditional form to send data to the application. However, many applications receive XHR requests from a JavaScript powered frontend. When using the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
20 method during an XHR request, Laravel will not generate a redirect response. Instead, Laravel generates a JSON response containing all of the validation errors. This JSON response will be sent with a 422 HTTP status code.The namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
48 Directive
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
You may use the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
48 Blade directive to quickly determine if validation error messages exist for a given attribute. Within an namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
48 directive, you may echo the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
51 variable to display the error message:Post Title
class="@error['title'] is-invalid @enderror">
{{ $message }}
If you are using named error bags, you may pass the name of the error bag as the second argument to the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
48 directive:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
0Repopulating Forms
When Laravel generates a redirect response due to a validation error, the framework will automatically flash all of the request's input to the session. This is done so that you may conveniently access the input during the next request and repopulate the form that the user attempted to submit.
To retrieve flashed input from the previous request, invoke the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
53 method on an instance of namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
27. The namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
53 method will pull the previously flashed input data from the session:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
1Laravel also provides a global
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
53 helper. If you are displaying old input within a Blade template, it is more convenient to use the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
53 helper to repopulate the form. If no old input exists for the given field, namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
58 will be returned:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
0A Note On Optional Fields
By default, Laravel includes the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
59 and namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
60 middleware in your application's global middleware stack. These middleware are listed in the stack by the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
61 class. Because of this, you will often need to mark your "optional" request fields as namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
62 if you do not want the validator to consider namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
58 values as invalid. For example:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
3In this example, we are specifying that the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
64 field may be either namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
58 or a valid date representation. If the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
62 modifier is not added to the rule definition, the validator would consider namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
58 an invalid date.Validation Error Response Format
When your application throws a
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
28 exception and the incoming HTTP request is expecting a JSON response, Laravel will automatically format the error messages for you and return a namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
69 HTTP response.Below, you can review an example of the JSON response format for validation errors. Note that nested error keys are flattened into "dot" notation format:
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
4Form Request Validation
Creating Form Requests
For more complex validation scenarios, you may wish to create a "form request". Form requests are custom request classes that encapsulate their own validation and authorization logic. To create a form request class, you may use the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
70 Artisan CLI command:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
5The generated form request class will be placed in the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
71 directory. If this directory does not exist, it will be created when you run the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
70 command. Each form request generated by Laravel has two methods: namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
73 and namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
74.As you might have guessed, the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
73 method is responsible for determining if the currently authenticated user can perform the action represented by the request, while the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
74 method returns the validation rules that should apply to the request's data:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
6Note
You may type-hint any dependencies you require within the74 method's signature. They will automatically be resolved via the Laravel service container.
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
So, how are the validation rules evaluated? All you need to do is type-hint the request on your controller method. The incoming form request is validated before the controller method is called, meaning you do not need to clutter your controller with any validation logic:
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
7If validation fails, a redirect response will be generated to send the user back to their previous location. The errors will also be flashed to the session so they are available for display. If the request was an XHR request, an HTTP response with a 422 status code will be returned to the user including a JSON representation of the validation errors.
Adding After Hooks To Form Requests
If you would like to add an "after" validation hook to a form request, you may use the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
78 method. This method receives the fully constructed validator, allowing you to call any of its methods before the validation rules are actually evaluated:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
8Stopping On First Validation Failure Attribute
By adding a
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
79 property to your request class, you may inform the validator that it should stop validating all attributes once a single validation failure has occurred:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
9Customizing The Redirect Location
As previously discussed, a redirect response will be generated to send the user back to their previous location when form request validation fails. However, you are free to customize this behavior. To do so, define a
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
80 property on your form request: * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
0Or, if you would like to redirect users to a named route, you may define a
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
81 property instead: * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
1Authorizing Form Requests
The form request class also contains an
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
73 method. Within this method, you may determine if the authenticated user actually has the authority to update a given resource. For example, you may determine if a user actually owns a blog comment they are attempting to update. Most likely, you will interact with your authorization gates and policies within this method: * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
2Since all form requests extend the base Laravel request class, we may use the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
83 method to access the currently authenticated user. Also, note the call to the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
84 method in the example above. This method grants you access to the URI parameters defined on the route being called, such as the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
85 parameter in the example below: * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
3Therefore, if your application is taking advantage of route model binding, your code may be made even more succinct by accessing the resolved model as a property of the request:
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
4If the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
73 method returns namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
87, an HTTP response with a 403 status code will automatically be returned and your controller method will not execute.If you plan to handle authorization logic for the request in another part of your application, you may simply return
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
88 from the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
73 method: * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
5Note
You may type-hint any dependencies you need within the73 method's signature. They will automatically be resolved via the Laravel service container.
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
Customizing The Error Messages
You may customize the error messages used by the form request by overriding the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
91 method. This method should return an array of attribute / rule pairs and their corresponding error messages: * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
6Customizing The Validation Attributes
Many of Laravel's built-in validation rule error messages contain an
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
92 placeholder. If you would like the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
92 placeholder of your validation message to be replaced with a custom attribute name, you may specify the custom names by overriding the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
94 method. This method should return an array of attribute / name pairs: * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
7Preparing Input For Validation
If you need to prepare or sanitize any data from the request before you apply your validation rules, you may use the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
95 method: * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
8Manually Creating Validators
If you do not want to use the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
20 method on the request, you may create a validator instance manually using the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
97 facade. The namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
98 method on the facade generates a new validator instance: * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
9The first argument passed to the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
98 method is the data under validation. The second argument is an array of the validation rules that should be applied to the data.After determining whether the request validation failed, you may use the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
00 method to flash the error messages to the session. When using this method, the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
38 variable will automatically be shared with your views after redirection, allowing you to easily display them back to the user. The * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
00 method accepts a validator, a * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
03, or a PHP * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
04.Stopping On First Validation Failure
The
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
79 method will inform the validator that it should stop validating all attributes once a single validation failure has occurred:$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
0Automatic Redirection
If you would like to create a validator instance manually but still take advantage of the automatic redirection offered by the HTTP request's
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
20 method, you may call the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
20 method on an existing validator instance. If validation fails, the user will automatically be redirected or, in the case of an XHR request, a JSON response will be returned:$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
1You may use the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
33 method to store the error messages in a named error bag if validation fails:$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
2Named Error Bags
If you have multiple forms on a single page, you may wish to name the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
03 containing the validation errors, allowing you to retrieve the error messages for a specific form. To achieve this, pass a name as the second argument to * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
00:$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
3You may then access the named
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
03 instance from the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
38 variable:$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
4Customizing The Error Messages
If needed, you may provide custom error messages that a validator instance should use instead of the default error messages provided by Laravel. There are several ways to specify custom messages. First, you may pass the custom messages as the third argument to the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
13 method:$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
5In this example, the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
92 placeholder will be replaced by the actual name of the field under validation. You may also utilize other placeholders in validation messages. For example:$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
6Specifying A Custom Message For A Given Attribute
Sometimes you may wish to specify a custom error message only for a specific attribute. You may do so using "dot" notation. Specify the attribute's name first, followed by the rule:
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
7Specifying Custom Attribute Values
Many of Laravel's built-in error messages include an
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
92 placeholder that is replaced with the name of the field or attribute under validation. To customize the values used to replace these placeholders for specific fields, you may pass an array of custom attributes as the fourth argument to the * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
13 method:$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
8After Validation Hook
You may also attach callbacks to be run after validation is completed. This allows you to easily perform further validation and even add more error messages to the message collection. To get started, call the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
17 method on a validator instance:$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
9Working With Validated Input
After validating incoming request data using a form request or a manually created validator instance, you may wish to retrieve the incoming request data that actually underwent validation. This can be accomplished in several ways. First, you may call the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
18 method on a form request or validator instance. This method returns an array of the data that was validated:$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
0Alternatively, you may call the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
19 method on a form request or validator instance. This method returns an instance of * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
20. This object exposes * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
21, * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
22, and * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
23 methods to retrieve a subset of the validated data or the entire array of validated data:$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
1In addition, the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
20 instance may be iterated over and accessed like an array:$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
2If you would like to add additional fields to the validated data, you may call the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
25 method:$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
3If you would like to retrieve the validated data as a collection instance, you may call the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
26 method:$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
4Working With Error Messages
After calling the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
27 method on a namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
97 instance, you will receive an namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
44 instance, which has a variety of convenient methods for working with error messages. The namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
38 variable that is automatically made available to all views is also an instance of the * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
03 class.Retrieving The First Error Message For A Field
To retrieve the first error message for a given field, use the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
32 method:$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
5Retrieving All Error Messages For A Field
If you need to retrieve an array of all the messages for a given field, use the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
33 method:$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
6If you are validating an array form field, you may retrieve all of the messages for each of the array elements using the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
34 character:$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
7Retrieving All Error Messages For All Fields
To retrieve an array of all messages for all fields, use the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
23 method:$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
8Determining If Messages Exist For A Field
The
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
36 method may be used to determine if any error messages exist for a given field:$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
9Specifying Custom Messages In Language Files
Laravel's built-in validation rules each have an error message that is located in your application's
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
46 file. Within this file, you will find a translation entry for each validation rule. You are free to change or modify these messages based on the needs of your application.In addition, you may copy this file to another translation language directory to translate the messages for your application's language. To learn more about Laravel localization, check out the complete localization documentation.
Custom Messages For Specific Attributes
You may customize the error messages used for specified attribute and rule combinations within your application's validation language files. To do so, add your message customizations to the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
38 array of your application's * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
39 language file: 'title' => 'bail|required|unique:posts|max:255',
0Specifying Attributes In Language Files
Many of Laravel's built-in error messages include an
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
92 placeholder that is replaced with the name of the field or attribute under validation. If you would like the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
92 portion of your validation message to be replaced with a custom value, you may specify the custom attribute name in the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
94 array of your * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
39 language file: 'title' => 'bail|required|unique:posts|max:255',
1Specifying Values In Language Files
Some of Laravel's built-in validation rule error messages contain a
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
44 placeholder that is replaced with the current value of the request attribute. However, you may occasionally need the * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
44 portion of your validation message to be replaced with a custom representation of the value. For example, consider the following rule that specifies that a credit card number is required if the * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
46 has a value of * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
47: 'title' => 'bail|required|unique:posts|max:255',
2If this validation rule fails, it will produce the following error message:
'title' => 'bail|required|unique:posts|max:255',
3Instead of displaying
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
47 as the payment type value, you may specify a more user-friendly value representation in your * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
39 language file by defining a * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
50 array:After defining this value, the validation rule will produce the following error message:
'title' => 'bail|required|unique:posts|max:255',
4Available Validation Rules
Below is a list of all available validation rules and their function:
accepted
The field under validation must be
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
51, * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
52, * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
53, or namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
88. This is useful for validating "Terms of Service" acceptance or similar fields.accepted_if:anotherfield,value,...
The field under validation must be
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
51, * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
52, * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
53, or namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
88 if another field under validation is equal to a specified value. This is useful for validating "Terms of Service" acceptance or similar fields.active_url
The field under validation must have a valid A or AAAA record according to the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
59 PHP function. The hostname of the provided URL is extracted using the * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
60 PHP function before being passed to * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
59.after:date
The field under validation must be a value after a given date. The dates will be passed into the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
62 PHP function in order to be converted to a valid * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
63 instance: 'title' => 'bail|required|unique:posts|max:255',
5Instead of passing a date string to be evaluated by
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
62, you may specify another field to compare against the date: 'title' => 'bail|required|unique:posts|max:255',
6after_or_equal:date
The field under validation must be a value after or equal to the given date. For more information, see the after rule.
alpha
The field under validation must be entirely alphabetic characters.
alpha_dash
The field under validation may have alpha-numeric characters, as well as dashes and underscores.
alpha_num
The field under validation must be entirely alpha-numeric characters.
array
The field under validation must be a PHP
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
04.When additional values are provided to the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
04 rule, each key in the input array must be present within the list of values provided to the rule. In the following example, the * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
67 key in the input array is invalid since it is not contained in the list of values provided to the * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
04 rule: 'title' => 'bail|required|unique:posts|max:255',
7In general, you should always specify the array keys that are allowed to be present within your array.
bail
Stop running validation rules for the field after the first validation failure.
While the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
34 rule will only stop validating a specific field when it encounters a validation failure, the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
79 method will inform the validator that it should stop validating all attributes once a single validation failure has occurred:$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
0before:date
The field under validation must be a value preceding the given date. The dates will be passed into the PHP
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
62 function in order to be converted into a valid * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
63 instance. In addition, like the * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
17 rule, the name of another field under validation may be supplied as the value of * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
74.before_or_equal:date
The field under validation must be a value preceding or equal to the given date. The dates will be passed into the PHP
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
62 function in order to be converted into a valid * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
63 instance. In addition, like the * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
17 rule, the name of another field under validation may be supplied as the value of * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
74.between:min,max
The field under validation must have a size between the given min and max [inclusive]. Strings, numerics, arrays, and files are evaluated in the same fashion as the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
79 rule.boolean
The field under validation must be able to be cast as a boolean. Accepted input are
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
88, namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
87, * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
53, * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
83, * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
84, and * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
85.confirmed
The field under validation must have a matching field of
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
86. For example, if the field under validation is * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
87, a matching * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
88 field must be present in the input.current_password
The field under validation must match the authenticated user's password. You may specify an authentication guard using the rule's first parameter:
'title' => 'bail|required|unique:posts|max:255',
9date
The field under validation must be a valid, non-relative date according to the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
62 PHP function.date_equals:date
The field under validation must be equal to the given date. The dates will be passed into the PHP
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
62 function in order to be converted into a valid * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
63 instance.date_format:format
The field under validation must match the given format. You should use either
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
74 or * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
93 when validating a field, not both. This validation rule supports all formats supported by PHP's DateTime class.declined
The field under validation must be
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
94, * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
95, * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
83, or namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
87.declined_if:anotherfield,value,...
The field under validation must be
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
94, * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
95, * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
83, or namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
87 if another field under validation is equal to a specified value.different:field
The field under validation must have a different value than field.
digits:value
The integer under validation must have an exact length of value.
digits_between:min,max
The integer validation must have a length between the given min and max.
dimensions
The file under validation must be an image meeting the dimension constraints as specified by the rule's parameters:
'title' => 'required|unique:posts|max:255',
'author.name' => 'required',
'author.description' => 'required',
0Available constraints are: min_width, max_width, min_height, max_height, width, height, ratio.
A ratio constraint should be represented as width divided by height. This can be specified either by a fraction like
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
02 or a float like $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
03: 'title' => 'required|unique:posts|max:255',
'author.name' => 'required',
'author.description' => 'required',
1Since this rule requires several arguments, you may use the
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
04 method to fluently construct the rule: 'title' => 'required|unique:posts|max:255',
'author.name' => 'required',
'author.description' => 'required',
2distinct
When validating arrays, the field under validation must not have any duplicate values:
Distinct uses loose variable comparisons by default. To use strict comparisons, you may add the
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
05 parameter to your validation rule definition: 'title' => 'required|unique:posts|max:255',
'author.name' => 'required',
'author.description' => 'required',
3You may add
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
06 to the validation rule's arguments to make the rule ignore capitalization differences: 'title' => 'required|unique:posts|max:255',
'author.name' => 'required',
'author.description' => 'required',
4doesnt_start_with:foo,bar,...
The field under validation must not start with one of the given values.
doesnt_end_with:foo,bar,...
The field under validation must not end with one of the given values.
The field under validation must be formatted as an email address. This validation rule utilizes the
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
07 package for validating the email address. By default, the $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
08 validator is applied, but you can apply other validation styles as well:The example above will apply the
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
08 and $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
10 validations. Here's a full list of validation styles you can apply:
11:$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
08$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
05:$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
14$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
15:$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
10$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
17:$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
18$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
19:$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
20$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
21:$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
22$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
The
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
19 validator, which uses PHP's $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
24 function, ships with Laravel and was Laravel's default email validation behavior prior to Laravel version 5.8.Warning
The15 and
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
17 validators require the PHP
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
27 extension.
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
ends_with:foo,bar,...
The field under validation must end with one of the given values.
enum
The
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
28 rule is a class based rule that validates whether the field under validation contains a valid enum value. The $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
28 rule accepts the name of the enum as its only constructor argument: 'title' => 'required|unique:posts|max:255',
'author.name' => 'required',
'author.description' => 'required',
5Warning
Enums are only available on PHP 8.1+.
exclude
The field under validation will be excluded from the request data returned by the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
20 and * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
18 methods.exclude_if:anotherfield,value
The field under validation will be excluded from the request data returned by the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
20 and * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
18 methods if the anotherfield field is equal to value.If complex conditional exclusion logic is required, you may utilize the
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
34 method. This method accepts a boolean or a closure. When given a closure, the closure should return namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
88 or namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
87 to indicate if the field under validation should be excluded: 'title' => 'required|unique:posts|max:255',
'author.name' => 'required',
'author.description' => 'required',
6exclude_unless:anotherfield,value
The field under validation will be excluded from the request data returned by the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
20 and * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
18 methods unless anotherfield's field is equal to value. If value is namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
58 [$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
40], the field under validation will be excluded unless the comparison field is namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
58 or the comparison field is missing from the request data.exclude_with:anotherfield
The field under validation will be excluded from the request data returned by the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
20 and * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
18 methods if the anotherfield field is present.exclude_without:anotherfield
The field under validation will be excluded from the request data returned by the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
20 and * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
18 methods if the anotherfield field is not present.exists:table,column
The field under validation must exist in a given database table.
Basic Usage Of Exists Rule
If the
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
46 option is not specified, the field name will be used. So, in this case, the rule will validate that the $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
47 database table contains a record with a $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
48 column value matching the request's $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
48 attribute value.Specifying A Custom Column Name
You may explicitly specify the database column name that should be used by the validation rule by placing it after the database table name:
'title' => 'required|unique:posts|max:255',
'author.name' => 'required',
'author.description' => 'required',
7Occasionally, you may need to specify a specific database connection to be used for the
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
50 query. You can accomplish this by prepending the connection name to the table name: 'title' => 'required|unique:posts|max:255',
'author.name' => 'required',
'author.description' => 'required',
8Instead of specifying the table name directly, you may specify the Eloquent model which should be used to determine the table name:
'title' => 'required|unique:posts|max:255',
'author.name' => 'required',
'author.description' => 'required',
9If you would like to customize the query executed by the validation rule, you may use the
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
51 class to fluently define the rule. In this example, we'll also specify the validation rules as an array instead of using the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
32 character to delimit them: 'title' => 'required|unique:posts|max:255',
0You may explicitly specify the database column name that should be used by the
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
50 rule generated by the $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
54 method by providing the column name as the second argument to the $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
50 method: 'title' => 'required|unique:posts|max:255',
1file
The field under validation must be a successfully uploaded file.
filled
The field under validation must not be empty when it is present.
gt:field
The field under validation must be greater than the given field. The two fields must be of the same type. Strings, numerics, arrays, and files are evaluated using the same conventions as the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
79 rule.gte:field
The field under validation must be greater than or equal to the given field. The two fields must be of the same type. Strings, numerics, arrays, and files are evaluated using the same conventions as the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
79 rule.image
The file under validation must be an image [jpg, jpeg, png, bmp, gif, svg, or webp].
in:foo,bar,...
The field under validation must be included in the given list of values. Since this rule often requires you to
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
58 an array, the $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
59 method may be used to fluently construct the rule: 'title' => 'required|unique:posts|max:255',
2When the
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
60 rule is combined with the * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
04 rule, each value in the input array must be present within the list of values provided to the $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
60 rule. In the following example, the $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
63 airport code in the input array is invalid since it is not contained in the list of airports provided to the $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
60 rule: 'title' => 'required|unique:posts|max:255',
3in_array:anotherfield.*
The field under validation must exist in anotherfield's values.
integer
The field under validation must be an integer.
Warning
This validation rule does not verify that the input is of the "integer" variable type, only that the input is of a type accepted by PHP's65 rule. If you need to validate the input as being a number please use this rule in combination with the
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
66 validation rule.
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
ip
The field under validation must be an IP address.
ipv4
The field under validation must be an IPv4 address.
ipv6
The field under validation must be an IPv6 address.
json
The field under validation must be a valid JSON string.
lt:field
The field under validation must be less than the given field. The two fields must be of the same type. Strings, numerics, arrays, and files are evaluated using the same conventions as the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
79 rule.lte:field
The field under validation must be less than or equal to the given field. The two fields must be of the same type. Strings, numerics, arrays, and files are evaluated using the same conventions as the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
79 rule.lowercase:field
The field under validation must be lowercase.
mac_address
The field under validation must be a MAC address.
max:value
The field under validation must be less than or equal to a maximum value. Strings, numerics, arrays, and files are evaluated in the same fashion as the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
79 rule.max_digits:value
The integer under validation must have a maximum length of value.
mimetypes:text/plain,...
The file under validation must match one of the given MIME types:
'title' => 'required|unique:posts|max:255',
4To determine the MIME type of the uploaded file, the file's contents will be read and the framework will attempt to guess the MIME type, which may be different from the client's provided MIME type.
mimes:foo,bar,...
The file under validation must have a MIME type corresponding to one of the listed extensions.
Basic Usage Of MIME Rule
'title' => 'required|unique:posts|max:255',
5Even though you only need to specify the extensions, this rule actually validates the MIME type of the file by reading the file's contents and guessing its MIME type. A full listing of MIME types and their corresponding extensions may be found at the following location:
//svn.apache.org/repos/asf/httpd/httpd/trunk/docs/conf/mime.types
min:value
The field under validation must have a minimum value. Strings, numerics, arrays, and files are evaluated in the same fashion as the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
79 rule.min_digits:value
The integer under validation must have a minimum length of value.
multiple_of:value
The field under validation must be a multiple of value.
Warning
The71 PHP extension is required in order to use the
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
72 rule.
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
not_in:foo,bar,...
The field under validation must not be included in the given list of values. The
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
73 method may be used to fluently construct the rule: 'title' => 'required|unique:posts|max:255',
6not_regex:pattern
The field under validation must not match the given regular expression.
Internally, this rule uses the PHP
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
74 function. The pattern specified should obey the same formatting required by $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
74 and thus also include valid delimiters. For example: $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
76.Warning
When using the77 /
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
78 patterns, it may be necessary to specify your validation rules using an array instead of using
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
32 delimiters, especially if the regular expression contains a
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
32 character.
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
nullable
The field under validation may be
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
58.numeric
The field under validation must be numeric.
password
The field under validation must match the authenticated user's password.
Warning
This rule was renamed to82 with the intention of removing it in Laravel 9. Please use the Current Password rule instead.
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
present
The field under validation must be present in the input data but can be empty.
prohibited
The field under validation must be an empty string or not present.
prohibited_if:anotherfield,value,...
The field under validation must be an empty string or not present if the anotherfield field is equal to any value.
If complex conditional prohibition logic is required, you may utilize the
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
83 method. This method accepts a boolean or a closure. When given a closure, the closure should return namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
88 or namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
87 to indicate if the field under validation should be prohibited: 'title' => 'required|unique:posts|max:255',
7prohibited_unless:anotherfield,value,...
The field under validation must be an empty string or not present unless the anotherfield field is equal to any value.
prohibits:anotherfield,...
If the field under validation is present, no fields in anotherfield can be present, even if empty.
regex:pattern
The field under validation must match the given regular expression.
Internally, this rule uses the PHP
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
74 function. The pattern specified should obey the same formatting required by $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
74 and thus also include valid delimiters. For example: $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
88.Warning
When using the77 /
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
78 patterns, it may be necessary to specify rules in an array instead of using
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
32 delimiters, especially if the regular expression contains a
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
32 character.
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
required
The field under validation must be present in the input data and not empty. A field is considered "empty" if one of the following conditions are true:
- The value is
58.namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
- The value is an empty string.
- The value is an empty array or empty
94 object.$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
- The value is an uploaded file with no path.
required_if:anotherfield,value,...
The field under validation must be present and not empty if the anotherfield field is equal to any value.
If you would like to construct a more complex condition for the
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
95 rule, you may use the $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
96 method. This method accepts a boolean or a closure. When passed a closure, the closure should return namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
88 or namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
87 to indicate if the field under validation is required: 'title' => 'required|unique:posts|max:255',
8required_unless:anotherfield,value,...
The field under validation must be present and not empty unless the anotherfield field is equal to any value. This also means anotherfield must be present in the request data unless value is
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
58. If value is namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
58 [$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
01], the field under validation will be required unless the comparison field is namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
58 or the comparison field is missing from the request data.required_with:foo,bar,...
The field under validation must be present and not empty only if any of the other specified fields are present and not empty.
required_with_all:foo,bar,...
The field under validation must be present and not empty only if all of the other specified fields are present and not empty.
required_without:foo,bar,...
The field under validation must be present and not empty only when any of the other specified fields are empty or not present.
required_without_all:foo,bar,...
The field under validation must be present and not empty only when all of the other specified fields are empty or not present.
required_array_keys:foo,bar,...
The field under validation must be an array and must contain at least the specified keys.
same:field
The given field must match the field under validation.
size:value
The field under validation must have a size matching the given value. For string data, value corresponds to the number of characters. For numeric data, value corresponds to a given integer value [the attribute must also have the
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
66 or $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
04 rule]. For an array, size corresponds to the $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
05 of the array. For files, size corresponds to the file size in kilobytes. Let's look at some examples: 'title' => 'required|unique:posts|max:255',
9starts_with:foo,bar,...
The field under validation must start with one of the given values.
string
The field under validation must be a string. If you would like to allow the field to also be
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
58, you should assign the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
62 rule to the field.timezone
The field under validation must be a valid timezone identifier according to the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
08 PHP function.unique:table,column
The field under validation must not exist within the given database table.
Specifying A Custom Table / Column Name:
Instead of specifying the table name directly, you may specify the Eloquent model which should be used to determine the table name:
0
@foreach [$errors->all[] as $error]
The
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
46 option may be used to specify the field's corresponding database column. If the $validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
46 option is not specified, the name of the field under validation will be used.1
@foreach [$errors->all[] as $error]
Specifying A Custom Database Connection
Occasionally, you may need to set a custom connection for database queries made by the Validator. To accomplish this, you may prepend the connection name to the table name:
2
@foreach [$errors->all[] as $error]
Forcing A Unique Rule To Ignore A Given ID:
Sometimes, you may wish to ignore a given ID during unique validation. For example, consider an "update profile" screen that includes the user's name, email address, and location. You will probably want to verify that the email address is unique. However, if the user only changes the name field and not the email field, you do not want a validation error to be thrown because the user is already the owner of the email address in question.
To instruct the validator to ignore the user's ID, we'll use the
$validatedData = $request->validate[[
'title' => ['required', 'unique:posts', 'max:255'],
51 class to fluently define the rule. In this example, we'll also specify the validation rules as an array instead of using the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
32 character to delimit the rules:3
@foreach [$errors->all[] as $error]
Warning
You should never pass any user controlled request input into the13 method. Instead, you should only pass a system generated unique ID such as an auto-incrementing ID or UUID from an Eloquent model instance. Otherwise, your application will be vulnerable to an SQL injection attack.
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
Instead of passing the model key's value to the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
13 method, you may also pass the entire model instance. Laravel will automatically extract the key from the model:4
@foreach [$errors->all[] as $error]
If your table uses a primary key column name other than
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
15, you may specify the name of the column when calling the $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
13 method:5
@foreach [$errors->all[] as $error]
By default, the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
35 rule will check the uniqueness of the column matching the name of the attribute being validated. However, you may pass a different column name as the second argument to the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
35 method:6
@foreach [$errors->all[] as $error]
Adding Additional Where Clauses:
You may specify additional query conditions by customizing the query using the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
19 method. For example, let's add a query condition that scopes the query to only search records that have an $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
20 column value of * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
53:7
@foreach [$errors->all[] as $error]
uppercase:field
The field under validation must be uppercase.
url
The field under validation must be a valid URL.
uuid
The field under validation must be a valid RFC 4122 [version 1, 3, 4, or 5] universally unique identifier [UUID].
Conditionally Adding Rules
Skipping Validation When Fields Have Certain Values
You may occasionally wish to not validate a given field if another field has a given value. You may accomplish this using the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
22 validation rule. In this example, the $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
23 and $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
24 fields will not be validated if the $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
25 field has a value of namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
87:8
@foreach [$errors->all[] as $error]
Alternatively, you may use the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
27 rule to not validate a given field unless another field has a given value:9
@foreach [$errors->all[] as $error]
Validating When Present
In some situations, you may wish to run validation checks against a field only if that field is present in the data being validated. To quickly accomplish this, add the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
28 rule to your rule list:Post Title
class="@error['title'] is-invalid @enderror">
{{ $message }}
0In the example above, the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
29 field will only be validated if it is present in the $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
30 array.Note
If you are attempting to validate a field that should always be present but may be empty, check out this note on optional fields.
Complex Conditional Validation
Sometimes you may wish to add validation rules based on more complex conditional logic. For example, you may wish to require a given field only if another field has a greater value than 100. Or, you may need two fields to have a given value only when another field is present. Adding these validation rules doesn't have to be a pain. First, create a
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
97 instance with your static rules that never change:Post Title
class="@error['title'] is-invalid @enderror">
{{ $message }}
1Let's assume our web application is for game collectors. If a game collector registers with our application and they own more than 100 games, we want them to explain why they own so many games. For example, perhaps they run a game resale shop, or maybe they just enjoy collecting games. To conditionally add this requirement, we can use the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
28 method on the namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
97 instance.Post Title
class="@error['title'] is-invalid @enderror">
{{ $message }}
2The first argument passed to the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
28 method is the name of the field we are conditionally validating. The second argument is a list of the rules we want to add. If the closure passed as the third argument returns namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
88, the rules will be added. This method makes it a breeze to build complex conditional validations. You may even add conditional validations for several fields at once:Post Title
class="@error['title'] is-invalid @enderror">
{{ $message }}
3Note
The36 parameter passed to your closure will be an instance of
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
37 and may be used to access your input and files under validation.
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
Complex Conditional Array Validation
Sometimes you may want to validate a field based on another field in the same nested array whose index you do not know. In these situations, you may allow your closure to receive a second argument which will be the current individual item in the array being validated:
Post Title
class="@error['title'] is-invalid @enderror">
{{ $message }}
4Like the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
36 parameter passed to the closure, the $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
39 parameter is an instance of $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
37 when the attribute data is an array; otherwise, it is a string.Validating Arrays
As discussed in the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
04 validation rule documentation, the * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
04 rule accepts a list of allowed array keys. If any additional keys are present within the array, validation will fail:Post Title
class="@error['title'] is-invalid @enderror">
{{ $message }}
5In general, you should always specify the array keys that are allowed to be present within your array. Otherwise, the validator's
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
20 and * @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
18 methods will return all of the validated data, including the array and all of its keys, even if those keys were not validated by other nested array validation rules.Validating Nested Array Input
Validating nested array based form input fields doesn't have to be a pain. You may use "dot notation" to validate attributes within an array. For example, if the incoming HTTP request contains a
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
45 field, you may validate it like so:Post Title
class="@error['title'] is-invalid @enderror">
{{ $message }}
6You may also validate each element of an array. For example, to validate that each email in a given array input field is unique, you may do the following:
Post Title
class="@error['title'] is-invalid @enderror">
{{ $message }}
7Likewise, you may use the
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
$validated = $request->validate[[
'title' => 'required|unique:posts|max:255',
// The blog post is valid...
34 character when specifying custom validation messages in your language files, making it a breeze to use a single validation message for array based fields:Post Title
class="@error['title'] is-invalid @enderror">
{{ $message }}
8Accessing Nested Array Data
Sometimes you may need to access the value for a given nested array element when assigning validation rules to the attribute. You may accomplish this using the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
47 method. The $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
48 method accepts a closure that will be invoked for each iteration of the array attribute under validation and will receive the attribute's value and explicit, fully-expanded attribute name. The closure should return an array of rules to assign to the array element:Post Title
class="@error['title'] is-invalid @enderror">
{{ $message }}
9Error Message Indexes & Positions
When validating arrays, you may want to reference the index or position of a particular item that failed validation within the error message displayed by your application. To accomplish this, you may include the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
49 and $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
50 place-holders within your custom validation message:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
00Given the example above, validation will fail and the user will be presented with the following error of "Please describe photo #2."
Validating Files
Laravel provides a variety of validation rules that may be used to validate uploaded files, such as
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
51, $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
52, $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
53, and namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
37. While you are free to specify these rules individually when validating files, Laravel also offers a fluent file validation rule builder that you may find convenient:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
01If your application accepts images uploaded by your users, you may use the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
55 rule's $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
52 constructor method to indicate that the uploaded file should be an image. In addition, the $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
57 rule may be used to limit the dimensions of the image:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
02Note
More information regarding validating image dimensions may be found in the dimension rule documentation.
File Types
Even though you only need to specify the extensions when invoking the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
58 method, this method actually validates the MIME type of the file by reading the file's contents and guessing its MIME type. A full listing of MIME types and their corresponding extensions may be found at the following location://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/conf/mime.types
Validating Passwords
To ensure that passwords have an adequate level of complexity, you may use Laravel's
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
59 rule object:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
03The
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
59 rule object allows you to easily customize the password complexity requirements for your application, such as specifying that passwords require at least one letter, number, symbol, or characters with mixed casing:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
04In addition, you may ensure that a password has not been compromised in a public password data breach leak using the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
61 method:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
05Internally, the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
59 rule object uses the k-Anonymity model to determine if a password has been leaked via the haveibeenpwned.com service without sacrificing the user's privacy or security.By default, if a password appears at least once in a data leak, it will be considered compromised. You can customize this threshold using the first argument of the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
61 method:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
06Of course, you may chain all the methods in the examples above:
Defining Default Password Rules
You may find it convenient to specify the default validation rules for passwords in a single location of your application. You can easily accomplish this using the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
64 method, which accepts a closure. The closure given to the $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
65 method should return the default configuration of the Password rule. Typically, the $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
65 rule should be called within the $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
67 method of one of your application's service providers:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
07Then, when you would like to apply the default rules to a particular password undergoing validation, you may invoke the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
65 method with no arguments:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
08Occasionally, you may want to attach additional validation rules to your default password validation rules. You may use the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
74 method to accomplish this:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
09Custom Validation Rules
Using Rule Objects
Laravel provides a variety of helpful validation rules; however, you may wish to specify some of your own. One method of registering custom validation rules is using rule objects. To generate a new rule object, you may use the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
70 Artisan command. Let's use this command to generate a rule that verifies a string is uppercase. Laravel will place the new rule in the $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
71 directory. If this directory does not exist, Laravel will create it when you execute the Artisan command to create your rule:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
10Once the rule has been created, we are ready to define its behavior. A rule object contains a single method:
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
72. This method receives the attribute name, its value, and a callback that should be invoked on failure with the validation error message:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
11Once the rule has been defined, you may attach it to a validator by passing an instance of the rule object with your other validation rules:
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
12Translating Validation Messages
Instead of providing a literal error message to the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
73 closure, you may also provide a translation string key and instruct Laravel to translate the error message:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
13If necessary, you may provide placeholder replacements and the preferred language as the first and second arguments to the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
74 method:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
14Accessing Additional Data
If your custom validation rule class needs to access all of the other data undergoing validation, your rule class may implement the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
75 interface. This interface requires your class to define a $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
76 method. This method will automatically be invoked by Laravel [before validation proceeds] with all of the data under validation:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
15Or, if your validation rule requires access to the validator instance performing the validation, you may implement the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
77 interface:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
16Using Closures
If you only need the functionality of a custom rule once throughout your application, you may use a closure instead of a rule object. The closure receives the attribute's name, the attribute's value, and a
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
73 callback that should be called if validation fails:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
17Implicit Rules
By default, when an attribute being validated is not present or contains an empty string, normal validation rules, including custom rules, are not run. For example, the
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
35 rule will not be run against an empty string:namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class PostController extends Controller
* Show the form to create a new blog post.
* @return \Illuminate\View\View
return view['post.create'];
* @param \Illuminate\Http\Request $request
* @return \Illuminate\Http\Response
public function store[Request $request]
// Validate and store the blog post...
18For a custom rule to run even when an attribute is empty, the rule must imply that the attribute is required. To quickly generate a new implicit rule object, you may use the
$validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
70 Artisan command with the $validatedData = $request->validateWithBag['post', [
'title' => ['required', 'unique:posts', 'max:255'],
81 option: