Import facades directly instead of importing the aliases

[funkjedi]

Updated to import the facades directly instead of importing the aliases.

Allows package to be used without having to include the alias. Also prevents package from breaking if Laravel specific aliases (Log, Cache, Config, etc...) have been removed from config/app.php.

[austinheap]

Hey @funkjedi, what's the motivation behind this? If someone is using a different Facade for Log/Cache/etc then wouldn't this bypass it?

[funkjedi]

That's exactly the scenario we want to avoid. For example if a Laravel app defines the following class:

// doesn't implement \Psr\Log\LoggerInterface like we
// are expecting when we use \Log expecting it to be a facade
class Log {
	public function send() {
		//
	}
}

Because it exists in the global namespace the class alias for the Log facade won't be created by Laravel.

If it was someones intention to actually replace a facade what they'd actually do is replace the underlying binding in the service container. That way when accessed via facade, helpers (i.e. info(), logger(), etc) or by using the service binding (i.e. App::make('log'), app('log'), etc) it's alway using the same implementation.

[austinheap]

Thanks @funkjedi!