gravityview /
GravityView
| 1 | <?php |
||
| 19 | class GravityView_Plugin_Hooks_ACF extends GravityView_Plugin_and_Theme_Hooks { |
||
| 20 | |||
| 21 | /** |
||
| 22 | * @inheritDoc |
||
| 23 | * @since TODO |
||
| 24 | */ |
||
| 25 | protected $function_name = 'acf'; |
||
| 26 | |||
| 27 | /** |
||
| 28 | * @since TODO |
||
| 29 | */ |
||
| 30 | protected function add_hooks() { |
||
| 35 | |||
| 36 | /** |
||
| 37 | * ACF needs $_POST['fields'] to be an array. GV supports both serialized array and array, so we just process earlier. |
||
| 38 | * |
||
| 39 | * @since TODO |
||
| 40 | * |
||
| 41 | * @return void |
||
| 42 | */ |
||
| 43 | private function fix_posted_fields() { |
||
| 50 | } |
||
| 51 | |||
| 52 | new GravityView_Plugin_Hooks_ACF; |
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.