Laravel constructor and middleware execution order

     Today, I want to refactor the code structure ：  
      
        BaseController.php  Place common middleware   
        class BaseController  
        {  
            public function __construct(){  
                $this->middleware('login');    
            }  
        }  
      
        IndexController.php  Inherit  BaseController  
        class IndexController extends BaseController  
        {  
            $user;  //  Store login user instances   
            public function __construct(){  
                parent::__constuct();  
                $this->user = Auth::user();  
            }  
        }  
      
        --------------------  
      
         Code above , Has been an error ！ Prompt that the user instance cannot be obtained ！  
         Various tests ,kernel.php, route.php, BaseController, middleware How to write it , wait , No problem found . Even doubted for a time  parent::__contruct() Wrong inheritance ...  
      
         Finally found , There is a problem with the execution order of constructor and middleware ：  
            1. Execute the constructor first   
            2. Then call the middleware   
         therefore , My problem is ,login Middleware requires users to log in , And the constructor executes first , Get user information directly , Not logged in yet ！  
      
      
         Baidu found an article , Describes the problem ：  
            https://laravel-china.org/topics/3218/laravel53-middleware-and-controller-construction-method-execution-sequence-problem  
      
        /*  
             It mentions a sentence ：  
                 Cannot be in constructor , Get... Directly session Variable or authenticated user instance ！ Because the middleware has not been started ！  
      
             This description is not accurate ！  
                 After the user logs in , In the constructor , Naturally get session Variable or authenticated user instance ！  
      
             The main reason is that the middleware was not implemented before ！ To put it bluntly, it's a matter of order ！  
        */  
      
         resolvent ：  
             Only in route.php  It's in   
                1> Or use  route::get()->middle('login')  
                2> Or use  route::get(['middleware' => 'login', xxx])  
             The best way , You should use routing groups  route::group(['middleware' => 'login'])  
      
             Or is it ：  
                 Discard the use of user instances in the controller   

Copy

Publisher ： Full stack programmer stack length , Reprint please indicate the source ：https://javaforall.cn/113214.html Link to the original text ：https://javaforall.cn