1 | <?php |
||
19 | class GravityView_Theme_Hooks_SiteOrigin extends GravityView_Plugin_and_Theme_Hooks { |
||
20 | |||
21 | protected $constant_name = 'SITEORIGIN_PANELS_VERSION'; |
||
22 | |||
23 | protected $class_name = 'SiteOrigin_Panels'; |
||
24 | |||
25 | protected $content_meta_keys = array( |
||
26 | 'panels_data' |
||
27 | ); |
||
28 | |||
29 | /** |
||
30 | * Add support for SiteOrigin storage of widget information |
||
31 | * |
||
32 | * @since 2.0.7 |
||
33 | * |
||
34 | * @param array $meta_keys |
||
35 | * @param null $post |
||
36 | * @param \GV\View_Collection $views |
||
37 | * |
||
38 | * @return array |
||
39 | */ |
||
40 | function merge_content_meta_keys( $meta_keys = array(), $post = null, & $views = null ) { |
||
70 | |||
71 | } |
||
72 | |||
73 | new GravityView_Theme_Hooks_SiteOrigin; |
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.