| 1 | <?php |
||
| 11 | class RequestTicketResponse extends AbstractScaleEngineResponse |
||
| 12 | { |
||
| 13 | /** |
||
| 14 | * Get the response from the command as a ScaleEngineTicket model. |
||
| 15 | * |
||
| 16 | * This takes the command given, ensures that it has a successful response, |
||
| 17 | * and converts the response into a ScaleEngineTicket model. |
||
| 18 | * |
||
| 19 | * @param OperationCommand $command The RequestTicket API call made. |
||
| 20 | * @param ScaleEngineTicketFactory $modelFactory The factory to use to |
||
| 21 | * create tickets. Will be created if not given. |
||
| 22 | * @return ScaleEngineTicket The ticket returned from the API request. |
||
| 23 | */ |
||
| 24 | public static function fromCommand(OperationCommand $command, ScaleEngineTicketFactory $modelFactory = null) |
||
| 30 | } |
||
| 31 |
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.