GitHub Access Token became invalid

It seems like the GitHub access token used for retrieving details about this repository from GitHub became invalid. This might prevent certain types of inspections from being run (in particular, everything related to pull requests).
Please ask an admin of your repository to re-new the access token on this website.
Completed
Push — master ( 88f370...1732e9 )
by Brad
06:19
created

FooGallery_Compatibility::__construct()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 7
Code Lines 5

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
cc 1
eloc 5
nc 1
nop 0
dl 0
loc 7
rs 9.4285
c 0
b 0
f 0
1
<?php
0 ignored issues
show
Coding Style Compatibility introduced by
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 15 and the first side effect is on line 8.

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
/**
3
 * FooGallery Compatibility Class for including all 3rd party plugin compatibilities
4
 * Created by bradvin
5
 * Date: 23/03/2018
6
 */
7
8
require_once( FOOGALLERY_PATH . 'includes/compatibility/class-autoptimize-compatibility.php' );
9
require_once( FOOGALLERY_PATH . 'includes/compatibility/class-foobox-compatibility.php' );
10
require_once( FOOGALLERY_PATH . 'includes/compatibility/class-polylang-compatibility.php' );
11
require_once( FOOGALLERY_PATH . 'includes/compatibility/class-responsive-lightbox-dfactory-compatibility.php' );
12
require_once( FOOGALLERY_PATH . 'includes/compatibility/class-wprocket-compatibility.php' );
13
14
if ( ! class_exists( 'FooGallery_Compatibility' ) ) {
15
	class FooGallery_Compatibility {
16
		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...
17
			new FooGallery_Autoptimize_Compatibility();
18
			new FooGallery_FooBox_Compatibility();
19
			new FooGallery_Polylang_Compatibility();
20
			new FooGallery_Responsive_Lightbox_dFactory_Compatibility();
21
			//new FooGallery_WPRocket_Compatibility(); this has not been fully tested
22
		}
23
	}
24
}