[5.1] Use laravel's log writer class instead of monolog.

[usm4n]

Our Laravel's cool Illuminate\Log\Writer already implements the Psr\Log\LoggerInterface interface. Using the Monolog logger for the Psr\Log\LoggerInterface binding bypasses the Logging event system of the laravel. For instance, I just wanted to log all the exceptions to the console for the quick view 👓 :

    public function boot(DispatcherContract $events)
    {
        parent::boot($events);

        $events->listen('illuminate.log',function($level, $message) {

             $output = new \Symfony\Component\Console\Output\ConsoleOutput(3);

             $output->writeln('Console Log::' . $level . ': ' . $message);
             $output->writeln("++++++++++++++++++++++++++++++++++++++++++++++++++++++");

        });

        //
    }

And found out that the events were not firing, because the Monolog\Logger was being injected for the Psr\Log\LoggerInterface.

I hope it all make sense :)

Usman.

[usm4n]

Psr\Log\LoggerInterfaced is already aliased in the Container : https://github.com/laravel/framework/blob/5.1/src/Illuminate/Foundation/Application.php#L1048

[GrahamCampbell]

Maybe this should go to 5.2, since it's not really broken atm, and could have undesired consequences.

[usm4n]

@GrahamCampbell let us see what Taylor says. I don't have any issues with this to go in 5.2.

[usm4n]

But as 5.1 is LTS, this should be fixed in 5.1 as well.

[GrahamCampbell]

But as 5.1 is LTS, this should be fixed in 5.1 as well.

Nothing is broken though, so it's not a fix.

[usm4n]

Yeah, but the behaviour is undesired IMHO.