Use of laravel repository mode

During coding Decoupling has always been a hot topic . Use MVC When developing design patterns , If you need to query the database / When operating the database, you have to directly reference the model , Call model . Follow the normal call method directly as shown below , Don't use Eloquent ORM You can't operate the database , So that is ORM It has a very large coupling with this controller .

$position =  Position::createPosition($params);
$position->users()->attach($userParams);
$position->permissions()->attach($permissionParams);

The controller aspect should be only return related Code that does not contain any logic , So in order to decouple, we should reference repository Design patterns .

repository Required development level

First we need to define an interface

<?php


namespace App\Http\Repositories\Interfaces;


use App\Http\Repositories\Interfaces\BaseRepositoryInterface;

interface UserRepositoryInterface extends BaseRepositoryInterface
{

}

You can build a basic level by yourself BaseInterface To encapsulate common and basic operation models , After creating the interface, start binding repository To implement the interface

<?php


namespace App\Http\Permission\Repositories\Eloquent;


use App\Http\Repositories\Eloquent\EloquentBaseRepository;
use App\Http\Permission\Repositories\Interfaces\UserRepositoryInterface;

class UserRepository extends EloquentBaseRepository implements UserRepositoryInterface
{

}

After you create it, you need to create it in ServiceProvider Register and bind the interface , Ensure that it is associated with the model layer .

        $this->app->bind(UserRepositoryInterface::class,function (){
            return new UserRepository(new User);
        });

After binding, you can create service Then use the constructor to convert the interface Into it You can write logic and related codes .