| 1 | <?php |
||
| 10 | abstract class AbstractUI { |
||
| 11 | |||
| 12 | use QuestionHelperTrait; |
||
| 13 | |||
| 14 | /** @var AbstractKeekoCommand */ |
||
| 15 | protected $command; |
||
| 16 | |||
| 17 | /** @var IOService */ |
||
| 18 | protected $io; |
||
| 19 | |||
| 20 | public function __construct(AbstractKeekoCommand $command) { |
||
| 24 | |||
| 25 | abstract public function show(); |
||
| 26 | |||
| 27 | /** |
||
| 28 | * @return HelperSet |
||
| 29 | */ |
||
| 30 | protected function getHelperSet() { |
||
| 33 | |||
| 34 | /** |
||
| 35 | * @return CommandService |
||
| 36 | */ |
||
| 37 | protected function getService() { |
||
| 40 | } |
For interface and abstract methods, it is impossible to infer the return type from the immediate code. In these cases, it is generally advisible to explicitly annotate these methods with a
@returndoc comment to communicate to implementors of these methods what they are expected to return.