| 1 | <?php declare(strict_types = 1); |
||
| 13 | class MethodGenerator extends FunctionGenerator |
||
| 14 | { |
||
| 15 | use VisibilityTrait; |
||
| 16 | use AbstractFinalTrait; |
||
| 17 | |||
| 18 | /** |
||
| 19 | * {@inheritdoc} |
||
| 20 | * @throws \InvalidArgumentException |
||
| 21 | */ |
||
| 22 | public function defLine(string $code) |
||
| 30 | |||
| 31 | /** |
||
| 32 | * {@inheritdoc} |
||
| 33 | */ |
||
| 34 | public function code(int $indentation = 0) : string |
||
| 42 | |||
| 43 | /** |
||
| 44 | * Build function definition. |
||
| 45 | * |
||
| 46 | * @return string Function definition |
||
| 47 | */ |
||
| 48 | protected function buildDefinition() |
||
| 57 | } |
||
| 58 |
If you return a value from a function or method, it should be a sub-type of the type that is given by the parent type f.e. an interface, or abstract method. This is more formally defined by the Lizkov substitution principle, and guarantees that classes that depend on the parent type can use any instance of a child type interchangably. This principle also belongs to the SOLID principles for object oriented design.
Let’s take a look at an example:
Our function
my_functionexpects aPostobject, and outputs the author of the post. The base classPostreturns a simple string and outputting a simple string will work just fine. However, the child classBlogPostwhich is a sub-type ofPostinstead decided to return anobject, and is therefore violating the SOLID principles. If aBlogPostwere passed tomy_function, PHP would not complain, but ultimately fail when executing thestrtouppercall in its body.