Completed
Push — develop ( e2ac27...b5f4d0 )
by Zack
04:24
created

GravityView_Field_Date_Created   A

Complexity

Total Complexity 3

Size/Duplication

Total Lines 25
Duplicated Lines 100 %

Coupling/Cohesion

Components 0
Dependencies 1
Metric Value
wmc 3
lcom 0
cbo 1
dl 25
loc 25
rs 10

2 Methods

Rating   Name   Duplication   Size   Complexity  
A __construct() 4 4 1
A field_options() 10 10 2

How to fix   Duplicated Code   

Duplicated Code

Duplicate code is one of the most pungent code smells. A rule that is often used is to re-structure code once it is duplicated in three or more places.

Common duplication problems, and corresponding solutions are:

1
<?php
2
3
/**
4
 * Add custom options for date fields
5
 */
6 View Code Duplication
class GravityView_Field_Date_Created extends GravityView_Field {
0 ignored issues
show
Duplication introduced by
This class seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
7
8
	var $name = 'date_created';
9
10
	var $search_operators = array( 'less_than', 'greater_than', 'is', 'isnot' );
11
12
	var $group = 'meta';
13
14
	public function __construct() {
15
		$this->label = esc_attr__( 'Date Created', 'gravityview' );
0 ignored issues
show
Bug introduced by
The property label cannot be accessed from this context as it is declared private in class GravityView_Field.

This check looks for access to properties that are not accessible from the current context.

If you need to make a property accessible to another context you can either raise its visibility level or provide an accessible getter in the defining class.

Loading history...
16
		parent::__construct();
17
	}
18
19
	function field_options( $field_options, $template_id, $field_id, $context, $input_type ) {
0 ignored issues
show
Best Practice introduced by
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...
20
21
		if( 'edit' === $context ) {
22
			return $field_options;
23
		}
24
25
		$this->add_field_support('date_display', $field_options );
26
27
		return $field_options;
28
	}
29
30
}
31
32
new GravityView_Field_Date_Created;
33