AbstractRule - Code Metrics - macder/wfv-validation - Measure and Improve Code Quality continuously with Scrutinizer

AbstractRule A
last analyzed 2018-04-24 04:07 UTC

↳ Parent: Project

Complexity

Total Complexity

Size/Duplication

Total Lines	32
Duplicated Lines	0 %

Coupling/Cohesion

Components	0
Dependencies	0

Importance

Changes

Metric	Value
dl	0
loc	32
rs	10
c	0
b	0
f	0
wmc	2
lcom	0
cbo	0

2 Methods

Rating	Name	Duplication	Size	Complexity
A	__construct()	0	3	1
A	template()	0	3	1

<?php

namespace WFV\Rules;
defined( 'ABSPATH' ) || die();

use WFV\Contract\ValidateInterface;

/**
 *
 *
 * @since 0.11.0
 */
abstract class AbstractRule implements ValidateInterface {

	/**
	 *
	 *
	 * @since 0.11.0
	 * @access protected
	 * @var RespectValidator
	 */
	protected $validator;

	/**
	 *
	 *
	 * @since 0.11.0
	 *
	 */
	public function __construct( $validator ) {
		$this->validator = $validator;
	}

	/**
	 * Returns the template array for the field under validation
	 *
	 * @since 0.11.0
	 *
	 * @return array
	 */
	public function template() {
		return $this->template;
class MyClass { }

$x = new MyClass();
$x->foo = true;
	}
}


1			<?php
			0 ignored issues – show Coding Style Compatibility introduced 2017-05-19 16:41 UTC by Report Bug Copy Issue Report For compatibility and reusability of your code, PSR1 recommends that a file should introduce either new symbols (like classes, functions, etc.) or have side-effects (like outputting something, or including other files), but not both at the same time. The first symbol is defined on line 12 and the first side effect is on line 3. The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file. The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place. To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1. Loading history...
2			namespace WFV\Rules;
3			defined( 'ABSPATH' ) \|\| die();
4
5			use WFV\Contract\ValidateInterface;
6
7			/**
8			*
9			*
10			* @since 0.11.0
11			*/
12			abstract class AbstractRule implements ValidateInterface {
13
14			/**
15			*
16			*
17			* @since 0.11.0
18			* @access protected
19			* @var RespectValidator
20			*/
21			protected $validator;
22
23			/**
24			*
25			*
26			* @since 0.11.0
27			*
28			*/
29			public function __construct( $validator ) {
30			$this->validator = $validator;
31			}
32
33			/**
34			* Returns the template array for the field under validation
35			*
36			* @since 0.11.0
37			*
38			* @return array
39			*/
40			public function template() {
41			return $this->template;
			0 ignored issues – show Bug introduced 2017-06-01 05:47 UTC by Report Bug Copy Issue Report The property `template` does not exist. Did you maybe forget to declare it? In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code: class MyClass { } $x = new MyClass(); $x->foo = true; Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion: class MyClass { public $foo; } $x = new MyClass(); $x->foo = true; Loading history...
42			}
43			}
44

macder / wfv-validation

AbstractRule A last analyzed 2018-04-24 04:07 UTC

Complexity

Size/Duplication

Coupling/Cohesion

Importance

2 Methods

Duplication Side-by-Side

Filter issues like

AbstractRule A
last analyzed 2018-04-24 04:07 UTC