Completed
Push — staging ( 78e662...0f9e2f )
by
unknown
05:16
created

YIKES_Mailchimp_ThirdParty_Integrations   A

Complexity

Total Complexity 3

Size/Duplication

Total Lines 20
Duplicated Lines 0 %

Coupling/Cohesion

Components 0
Dependencies 1

Test Coverage

Coverage 0%

Importance

Changes 0
Metric Value
dl 0
loc 20
ccs 0
cts 9
cp 0
rs 10
c 0
b 0
f 0
wmc 3
lcom 0
cbo 1

2 Methods

Rating   Name   Duplication   Size   Complexity  
A __construct() 0 3 1
A load_third_party_integrations() 0 8 2
1
<?php 
2
/*
3
*	All Third Party Integrations Loaded Here
4
*	@since 6.0.3
5
*/
6
class YIKES_Mailchimp_ThirdParty_Integrations {
0 ignored issues
show
Coding Style Compatibility introduced by
PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions.

You can fix this by adding a namespace to your class:

namespace YourVendor;

class YourClass { }

When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.

Loading history...
7
8
	function __construct() {
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...
9
		add_action( 'init', array( $this, 'load_third_party_integrations' ) );
10
	}
11
	
12
	/*
13
	*	Load any third party integrations
14
	*
15
	*/
16
	public function load_third_party_integrations() {
17
		// required..*
18
		include_once( ABSPATH . 'wp-admin/includes/plugin.php' );
19
		/* Visual Composer */
20
		if( is_plugin_active( 'js_composer/js_composer.php' ) ) {
21
			new YIKES_Mailchimp_Visual_Composer_Extension();
22
		}
23
	}
24
25
}
26