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 14 and the first side effect is on line 6.
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 GV;
3
4
/** If this file is called directly, abort. */
5
if ( ! defined( 'GRAVITYVIEW_DIR' ) ) {
6
die();
7
}
8
9
/**
10
* The default Request class.
11
*
12
* Finds out what Views are being requested.
13
*/
14
class Frontend_Request extends Request {
15
/**
16
* Bootstrap.
17
*
18
* @return void
19
*/
20
public function __construct() {
21
add_action( 'wp', array( $this, 'parse' ), 12 );
22
parent::__construct();
23
}
24
25
/**
26
* Parse the current WordPress context around the $post global.
27
*
28
* Called by the `wp` hook.
29
*
30
* @param \WP $wp The WordPress environment class. Unused.
31
*
32
* @internal
33
* @return void
34
*/
35
public function parse( $wp = null ) {
36
/** Nothing to do in an administrative context. */
37
if ( $this->is_admin() ) {
38
return;
39
}
40
41
/** The post might either be a gravityview, or contain gravityview shortcodes. */
gravityview /
GravityView
Gennady Kovshenin
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.