| 1 | <?php |
||
| 14 | class FileParser extends Application |
||
| 15 | { |
||
| 16 | /** |
||
| 17 | * Gets the name of the command based on input. |
||
| 18 | * |
||
| 19 | * @param InputInterface $input The input interface |
||
| 20 | * |
||
| 21 | * @return string The command name |
||
| 22 | */ |
||
| 23 | protected function getCommandName(InputInterface $input) |
||
| 27 | |||
| 28 | /** |
||
| 29 | * Gets the default commands that should always be available. |
||
| 30 | * |
||
| 31 | * @return array An array of default Command instances |
||
| 32 | */ |
||
| 33 | protected function getDefaultCommands() |
||
| 41 | |||
| 42 | /** |
||
| 43 | * Overridden so that the application doesn't expect the command |
||
| 44 | * name to be the first argument. |
||
| 45 | */ |
||
| 46 | public function getDefinition() |
||
| 53 | } |
||
| 54 |
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.