Detailed explanation of laravel container lazy loading and auth extension_PHP tutorial

Detailed explanation of laravel container lazy loading and auth extension

Yesterday, I followed the manual tutorial to write an Auth extension. According to the principle of package independence, I don’t want to use Auth::extend( ) This method is written in start.php. There is no doubt that I chose to register the extension driver in the service provider's register() method. However, things backfired...

Problem found

When I write this in LoauthServiceProvider:

The code is as follows:

public function register()
{
//
Auth::extend('loauth',function($app){});
}

Report error

The code is as follows:

Call to undefined method IlluminateSupportFacadesAuth::extend()

Find the reason

I was confused at that time. Looking for the reason, I suspected that Auth was not registered? I checked and found that it was registered because it can be used in routing; php artisan clear-compiled was useless. I was puzzled and even suspected that I accidentally modified the core class and re-downloaded the laravel package, but the problem remained.

After struggling all night, I finally focused on the $defer attribute of AuthServiceProvider.

According to the manual and comments, we know that the $defer attribute is used to delay loading of the service provider. To put it bluntly, it is to delay the execution of the register() method, which only needs to be combined with the provides() method. For example:

The code is as follows:

public function provides()
{
return array('auth');
}

This is the method in AuthServiceProvider. When the framework is initialized, the service providers will be loaded in sequence. If it is found that the service provider is protected $defer=true, its provides() method will be called, and the returned array contains The service name that needs to be loaded lazily, so that when we call Auth::METHOD() in a route, controller, or elsewhere, the provider's register() method will be called.

Identify the crux

Then the question is, since it is passive lazy loading, which means that when I call the Auth class method, the Auth class should be automatically instantiated. Why is it prompted that the method does not exist when I call it in the LoauthServiceProvider, but when I call it in the routing But it's okay.

I guess it is because of the priority issue. Maybe when the framework registers LoauthServiceProvider::register(), Auth has not been marked as lazy loading. This creates a sequence problem and any service provider that is loaded immediately cannot Call the lazy-loaded service in the register method.

After research, the evidence was successfully found in the core code IlluminateFoundationProviderRepository

The code is as follows:

public function load(Application $app, array $providers)
{
//...Omit
// We will go ahead and register all of the eagerly loaded providers with the
// application so their services can be registered with the application as
// a provided service. Then we will set the deferred service list on it.
foreach ($manifest['eager'] as $provider)
{
$app->register($this->createProvider($app, $provider));
}
//Lazy loading mark after immediate loading service
$app->setDeferredServices($manifest['deferred']);
}

Solution

Although the problem has been discovered, it does not mean that the problem has been solved. Modifying the core code is not a wise choice, so we can only find a solution in our own package. One solution is as follows:

The code is as follows:

public function register()
{
//
$authProvider = new IlluminateAuthAuthServiceProvider($this->app);
$authProvider->register();
Auth::extend('loauth',function($app){});
}

Since auth has not been registered yet, we manually call its register method to register it.

The above is the entire content of this article, I hope you all like it.

http://www.bkjia.com/PHPjc/962934.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/962934.htmlTechArticleDetailed explanation of laravel container lazy loading and auth extension Yesterday, I followed the manual tutorial to write an Auth extension, following the package independence In principle, I don’t want to write the method Auth::extend() in...