[5.3] Fixed runtime error for when facade root not set.

[itsa-sh]

I've stumbled upon the following error:

RuntimeException in Facade.php line 234:

A facade root has not been set.

Comparing the RouteServiceProvider to previous versions, only in 5.3 I have noticed the facade being used.

I personally don't like facades and thankfully Laravel has never forced me to use them, until this which is a minor tweak :)

[taylorotwell]

How did you trigger this error? How do you recreate it from a fresh Laravel instance?

[taylorotwell]

Also that $this->app['router'] call is exactly the same call a facade would make, so you might want to reconsider your dislike of them. :P

[itsa-sh]

When I say I dislike facades I meant the way in which a static call to a Facade is made such as Route::get over $this->app['router'] or app('router'). I understand it's a case of personal preference, but I believe the facade can be harder to read but I admit that's pedantic.

There are two things I did actually, first was to remove the 'aliases' array from config/app.php in order to prevent the use of these Facades (I believe < 5.3 it used to error when this was not an array, whereas now it doesn't - so I really love that).

The second thing (whilst I was dabbling) was inside App\Http\Kernel which extends the core, I simply set $bootstrappers from the parent to the same values except this one: 'Illuminate\Foundation\Bootstrap\RegisterFacades' which was omitted and the result of the exception above.