1 | <?php |
||
23 | trait FormActionControllerTrait |
||
24 | { |
||
25 | /** |
||
26 | * @todo |
||
27 | * |
||
28 | * @var string |
||
29 | */ |
||
30 | protected $formScope = MainScope::class; |
||
31 | |||
32 | /** |
||
33 | * In case an exception (any exception type) is thrown during the |
||
34 | * middlewares execution, it can be automatically caught by FormZ, and the |
||
35 | * request will be forwarded to an action of the controller. |
||
36 | * |
||
37 | * You can use it for instance to log your exception in some log service; to |
||
38 | * render a view that contains a message explaining to the user that |
||
39 | * something went wrong. |
||
40 | * |
||
41 | * Just override this method to return the name of an existing action of the |
||
42 | * controller. The method will have a single parameter which is the |
||
43 | * exception. |
||
44 | * |
||
45 | * @return string|null |
||
46 | */ |
||
47 | protected function actionForException(): ?string |
||
51 | |||
52 | /** |
||
53 | * IMPORTANT: if you need to override this method in your own controller, do |
||
54 | * not forget to call `parent::initializeAction()`! |
||
55 | */ |
||
56 | private function initializeFormz() |
||
77 | } |
||
78 |
In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:
Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion: