CLILogger::__construct() - Code Metrics - Buttress/IRC - Measure and Improve Code Quality continuously with Scrutinizer

CLILogger::__construct() A
last analyzed 2017-02-27 18:54 UTC

↳ Parent: CLILogger

Complexity

Conditions	1
Paths	1

Size

Total Lines	4
Code Lines	2

Duplication

Lines	0
Ratio	0 %

Importance

Changes

Metric	Value
cc	1
eloc	2
nc	1
nop	1
dl	0
loc	4
rs	10
c	0
b	0
f	0

<?php
namespace Buttress\IRC\Logger;

use Psr\Log\AbstractLogger;
use Psr\Log\LogLevel;

class CLILogger extends AbstractLogger
{

    protected $debug;

    function __construct($debug = false)

    {
        $this->debug = !!$debug;
    }

    /**
     * Logs with an arbitrary level.
     *
     * @param mixed  $level
     * @param string $message
     * @param array  $context
     * @return null
     */
    public function log($level, $message, array $context = array())
    {
        $stamp = date("[Y-m-d H:i:s] ");
        $output = "";

        $message = trim($message);

        switch ($level) {
            case LogLevel::DEBUG:
                if ($this->debug) {
                    $output = "{$stamp} {$message}";
                }
                break;

            default:
                $output = "{$stamp} {$message}";
                break;
        }

        echo $output . PHP_EOL;

        if ($context) {

            var_dump($context);

            echo PHP_EOL;
        }
    }

}


1			<?php
2			namespace Buttress\IRC\Logger;
3
4			use Psr\Log\AbstractLogger;
5			use Psr\Log\LogLevel;
6
7			class CLILogger extends AbstractLogger
8			{
9
10			protected $debug;
11
12			function __construct($debug = false)
			0 ignored issues – show Best Practice introduced 2017-02-22 21:07 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
13			{
14			$this->debug = !!$debug;
15			}
16
17			/**
18			* Logs with an arbitrary level.
19			*
20			* @param mixed $level
21			* @param string $message
22			* @param array $context
23			* @return null
24			*/
25			public function log($level, $message, array $context = array())
26			{
27			$stamp = date("[Y-m-d H:i:s] ");
28			$output = "";
29
30			$message = trim($message);
31
32			switch ($level) {
33			case LogLevel::DEBUG:
34			if ($this->debug) {
35			$output = "{$stamp} {$message}";
36			}
37			break;
38
39			default:
40			$output = "{$stamp} {$message}";
41			break;
42			}
43
44			echo $output . PHP_EOL;
45
46			if ($context) {
			0 ignored issues – show Bug Best Practice introduced 2017-02-22 21:07 UTC by Report Bug Copy Issue Report The expression `$context` of type `array` is implicitly converted to a boolean; are you sure this is intended? If so, consider using `! empty($expr)` instead to make it clear that you intend to check for an array without elements. This check marks implicit conversions of arrays to boolean values in a comparison. While in PHP an empty array is considered to be equal (but not identical) to false, this is not always apparent. Consider making the comparison explicit by using `empty(..)` or `! empty(...)` instead. Loading history...
47			var_dump($context);
			0 ignored issues – show Security Debugging Code introduced 2017-02-22 21:07 UTC by Report Bug Copy Issue Report `var_dump($context);` looks like debug code. Are you sure you do not want to remove it? This might expose sensitive data. Loading history...
48			echo PHP_EOL;
49			}
50			}
51
52			}
53

Buttress / IRC

CLILogger::__construct() A last analyzed 2017-02-27 18:54 UTC

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like

CLILogger::__construct() A
last analyzed 2017-02-27 18:54 UTC