These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
| 1 | <?php |
||
| 2 | |||
| 3 | /** |
||
| 4 | * Author: mickael Louzet @micklouzet |
||
| 5 | * File: AbstractSearcher.php |
||
| 6 | * Created: 05/12/2019 |
||
| 7 | */ |
||
| 8 | |||
| 9 | declare(strict_types=1); |
||
| 10 | |||
| 11 | namespace Louzet\ComposerLockFileParser; |
||
| 12 | |||
| 13 | abstract class AbstractSearcher { |
||
| 14 | |||
| 15 | abstract public function vendorName(string $vendorName = ''); |
||
|
0 ignored issues
–
show
|
|||
| 16 | } |
||
| 17 |
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.