AbstractStorage::addAvailableMetric() - Code Metrics - Inspection of "supporting custom metrics" - philiplb/PHPProm - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Push — master ( 3c7a07...1bc614 )

by Philip

created 2016-11-06 19:39 UTC

AbstractStorage::addAvailableMetric() A

↳ Parent: AbstractStorage

Complexity

Conditions	1
Paths	1

Size

Total Lines	10
Code Lines	8

Duplication

Lines	0
Ratio	0 %

Importance

Changes

Metric	Value
c	0
b	0
f	0
dl	0
loc	10
rs	9.4285
cc	1
eloc	8
nc	1
nop	6

<?php

/*
 * This file is part of the PHPProm package.
 *
 * (c) Philip Lehmann-Böhm <[email protected]>
 *
 * For the full copyright and license information, please view the LICENSE
 * file that was distributed with this source code.
 */

namespace PHPProm\Storage;

abstract class AbstractStorage {

    protected $availableMetrics;

    public function __construct() {
        $this->availableMetrics = [];
    }

    public function addAvailableMetric($storagePrefix, $metric, $label, $help, $type, $defaultValue) {
        $this->availableMetrics[] = [
            'storagePrefix' => $storagePrefix,
            'metric' => $metric,
            'label' => $label,
            'help' => $help,
            'type' => $type,
            'defaultValue' => $defaultValue
        ];
    }

    public function getAvailableMetrics() {
        return $this->availableMetrics;
    }

    abstract public function storeMeasurement($prefix, $key, $value);


    abstract public function incrementMeasurement($prefix, $key);


    abstract public function getMeasurements($prefix, array $keys, $defaultValue = 'Nan');


}


1			<?php
2
3			/*
4			* This file is part of the PHPProm package.
5			*
6			* (c) Philip Lehmann-Böhm <[email protected]>
7			*
8			* For the full copyright and license information, please view the LICENSE
9			* file that was distributed with this source code.
10			*/
11
12			namespace PHPProm\Storage;
13
14			abstract class AbstractStorage {
15
16			protected $availableMetrics;
17
18			public function __construct() {
19			$this->availableMetrics = [];
20			}
21
22			public function addAvailableMetric($storagePrefix, $metric, $label, $help, $type, $defaultValue) {
23			$this->availableMetrics[] = [
24			'storagePrefix' => $storagePrefix,
25			'metric' => $metric,
26			'label' => $label,
27			'help' => $help,
28			'type' => $type,
29			'defaultValue' => $defaultValue
30			];
31			}
32
33			public function getAvailableMetrics() {
34			return $this->availableMetrics;
35			}
36
37			abstract public function storeMeasurement($prefix, $key, $value);
			0 ignored issues – show Documentation introduced 2016-11-06 00:25 UTC by Report Bug Copy Issue Report For interfaces and abstract methods it is generally a good practice to add a `@return` annotation even if it is just `@return void` or `@return null`, so that implementors know what to do in the overridden method. For interface and abstract methods, it is impossible to infer the return type from the immediate code. In these cases, it is generally advisible to explicitly annotate these methods with a `@return` doc comment to communicate to implementors of these methods what they are expected to return. Loading history...
38
39			abstract public function incrementMeasurement($prefix, $key);
			0 ignored issues – show Documentation introduced 2016-11-06 19:41 UTC by Report Bug Copy Issue Report For interfaces and abstract methods it is generally a good practice to add a `@return` annotation even if it is just `@return void` or `@return null`, so that implementors know what to do in the overridden method. For interface and abstract methods, it is impossible to infer the return type from the immediate code. In these cases, it is generally advisible to explicitly annotate these methods with a `@return` doc comment to communicate to implementors of these methods what they are expected to return. Loading history...
40
41			abstract public function getMeasurements($prefix, array $keys, $defaultValue = 'Nan');
			0 ignored issues – show Documentation introduced 2016-11-06 19:41 UTC by Report Bug Copy Issue Report For interfaces and abstract methods it is generally a good practice to add a `@return` annotation even if it is just `@return void` or `@return null`, so that implementors know what to do in the overridden method. For interface and abstract methods, it is impossible to infer the return type from the immediate code. In these cases, it is generally advisible to explicitly annotate these methods with a `@return` doc comment to communicate to implementors of these methods what they are expected to return. Loading history...
42
43			}
44

philiplb / PHPProm

Push — master ( 3c7a07...1bc614 )

AbstractStorage::addAvailableMetric() A

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like