| 1 | <?php |
||
| 17 | class BehaviorAlbum extends Behavior |
||
| 18 | { |
||
| 19 | /** |
||
| 20 | * Load Album model by conditions. |
||
| 21 | * |
||
| 22 | * @param array $conditions |
||
| 23 | * |
||
| 24 | * @return Album|ActiveRecordInterface|null |
||
| 25 | */ |
||
| 26 | protected function loadModel(array $conditions) |
||
| 30 | |||
| 31 | /** |
||
| 32 | * Remove owner of Album model. |
||
| 33 | * |
||
| 34 | * @param int $ownerId |
||
| 35 | * @param string $owner |
||
| 36 | * @param string $ownerAttribute |
||
| 37 | * |
||
| 38 | * @return bool |
||
| 39 | */ |
||
| 40 | protected function removeOwner(int $ownerId, string $owner, string $ownerAttribute): bool |
||
| 44 | } |
||
| 45 |
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.