Simplifying Validation in ThinkPHP with an AOP‑Style BaseValidate Class

In this tutorial we demonstrate how to compress repetitive validation code in a ThinkPHP project by introducing an AOP‑style BaseValidate class.

First, we examine the directory structure and create a common/validate folder containing a BaseValidate.php file that extends think\Validate .

The BaseValidate class provides a goCheck($data = null) method which automatically retrieves request parameters when none are supplied, runs the validation, and returns a JSON error response on failure.

<code>&lt;?php
namespace app\common\validate;
use app\common\controller\Base;
use think\Request;
use think\Validate;

class BaseValidate extends Validate
{
    /**
     * 基础类控制器
     * @param null|array $data
     * @return bool
     */
    public function goCheck($data = null)
    {
        // 当 data 不存在的时候去自动校验获取到的参数
        if (is_null($data)) {
            // 获取待验证的参数
            $data = Request::instance()->param();
        }
        // 进行验证
        if (!$this->check($data)) {
            (new Base())->ajaxjson(Base::error, $this->getError()); // 抛出的自定义异常
        }
        return true;
    }
}
</code>

After integrating this base validator, controllers can simply call (new YourValidate())->goCheck(); , eliminating duplicated validation logic across modules.

The article also shows a second optimization where the is_null check is refined to allow direct data passing, reducing the need to re‑fetch parameters inside controllers.

Overall, applying AOP principles to validation code makes the application more modular, reduces redundancy, and improves maintainability.