Specific use of ThinkPHP5 validator

This article mainly introduces the specific use of ThinkPHP5 validator, which has certain reference value. Now I share it with everyone. Friends in need can refer to it

Foreword:

When we are doing API development, we will accept parameters from the client. Everyone knows that this parameter is not trustworthy. Our back-end developers must verify this parameter. . I only knew about the tp5 validator in previous development, but I didn't know its purpose, because the previous development verification was often based on model fields. The validator is more suitable for API development. Today I will briefly talk about the use of the validator

Directory:

1. Create a validator

2. Write a separate validator

3. Call verification

1. Create a validator

First we need a folder to store our validator. We create a folder at the same level as the controller under the module and name it validate

Then we can create the validator. We only need to create a class and inherit the validate class of tp5.

But friends who are familiar with object-oriented thinking must know that when we need a method that must be used by every validator, but do not modify the source code of tp5. We will write one more class as our base class. All validators inherit this base class, and then this base class inherits the validate class of tp5.

Here we name it baseValidate

Now let’s create a serious validator. For example:

Then instantiate it in the controller or model and then call

The application of such a validator is now written. Let's see if there's anything we can simplify.

1. First of all, the data that needs to be verified is what we receive from the client. Then, the first step is to accept the data

2. Then we have to The data is verified. If the verification fails, the error message

is returned. These two steps are performed every time the interface is requested. Then we want to encapsulate this into BaseValidate

After the goCheck method is encapsulated, someone may ask, where is the verification rule? Woolen cloth?

2. Write a separate validator

#I have said before that BaseValidate is used to be inherited, so for the real validator, we also Didn't start writing. The rules are formulated into this validator. For a deeper understanding, here is an example using custom validation rules. In fact, the verification rules written by tp should be sufficient.

Let’s take the most commonly accepted data as an example, which is id. Normally, this id represents the id of a certain piece of data in our database. We often design this id as an unsigned auto-incrementing primary key, which is translated into human language as a positive integer. Then if the parameter passed by the customer is a negative number or a decimal, it should not pass the verification.

We create a validator based on the above requirements. The location is still the same as before in the validate folder

and is named IdMustBePositiveInt.php (the name is a bit long, but fortunately the text is clear)

First of all, we must inherit our basic validator

and then formulate rules to assign a value to a fixed member variable

So how to do custom rules? It’s actually simple. Define a protected method

! ! Note: If the judgment fails here: the return is not false but an error message.

3. Call verification

According to our previous encapsulation, the effect we need to achieve is to accept parameters and verify the parameters as one. So now how do we call verification?

Here comes the awesome one, let’s take ID as an example

1. ##Just this one line of code can directly complete the verification. When we instantiate the id validator, we call the goCheck method of its parent class.

2. The goCheck method will accept parameters and pass the parameters into the check method on the validate object

3. will match what we have in the id validator The require rules specified in $rule and our custom rules.

4. If all pass, it will return true

5. If one of them does not match, an exception will be thrown

这次只举了id为例子，虽然看上去比直接写独立验证麻烦很多，但是大家仔细想想，这个验证规则其实在很多地方都是一样的，比如密码验证规则，用户名验证规则等，当这个项目写完了。你已经完成了很多验证器。其实在下个项目中还可以继续套用的哦

TP5验证规则使用

①静态调用（使用内置的规则验证单个数据，返回值为布尔值）

②模型验证（在模型中的验证方式）

③控制器验证（控制器中进行验证）

如果你需要在控制器中进行验证，并且继承了\think\Controller的话，可以调用控制器类提供的validate方法进行验证，如下：

控制器中的验证代码可以简化为：

如果要使用场景，可以使用：

在validate方法中还支持做一些前置的操作回调，使用方式如下：

好了,本次tp5验证器的介绍了就写到这里了,希望对大家的学习有所帮助。

相关推荐：

ThinkPHP5.0框架控制器继承基与自定义类案例详解

Thinkphp5 前置操作详解

The above is the detailed content of Specific use of ThinkPHP5 validator. For more information, please follow other related articles on the PHP Chinese website!