We could not synchronize checks via GitHub's checks API since Scrutinizer's GitHub App is not installed for this repository.
| 1 | <?php |
||
| 21 | final class StandardResult implements Result |
||
| 22 | { |
||
| 23 | /** |
||
| 24 | * @var bool |
||
| 25 | */ |
||
| 26 | private $isValid; |
||
| 27 | |||
| 28 | /** |
||
| 29 | * @var mixed |
||
| 30 | */ |
||
| 31 | private $input; |
||
| 32 | |||
| 33 | /** |
||
| 34 | * @var Rule |
||
| 35 | */ |
||
| 36 | private $rule; |
||
| 37 | |||
| 38 | /** |
||
| 39 | * @var Rule[] |
||
| 40 | */ |
||
| 41 | private $children; |
||
| 42 | |||
| 43 | /** |
||
| 44 | * @var array |
||
| 45 | */ |
||
| 46 | private $properties; |
||
| 47 | |||
| 48 | /** |
||
| 49 | * @param bool $isValid |
||
| 50 | * @param mixed $input |
||
| 51 | * @param Rule $rule |
||
| 52 | * @param array $properties |
||
| 53 | * @param Result $children... |
||
|
|
|||
| 54 | */ |
||
| 55 | public function __construct($isValid, $input, Rule $rule, array $properties = [], Result ...$children) |
||
| 63 | |||
| 64 | /** |
||
| 65 | * {@inheritdoc} |
||
| 66 | */ |
||
| 67 | public function isValid() |
||
| 71 | |||
| 72 | /** |
||
| 73 | * {@inheritdoc} |
||
| 74 | */ |
||
| 75 | public function getInput() |
||
| 79 | |||
| 80 | /** |
||
| 81 | * {@inheritdoc} |
||
| 82 | */ |
||
| 83 | public function getRule() |
||
| 87 | |||
| 88 | /** |
||
| 89 | * {@inheritdoc} |
||
| 90 | */ |
||
| 91 | public function getChildren() |
||
| 95 | |||
| 96 | /** |
||
| 97 | * {@inheritdoc} |
||
| 98 | */ |
||
| 99 | public function getProperties() |
||
| 103 | |||
| 104 | /** |
||
| 105 | * {@inheritdoc} |
||
| 106 | */ |
||
| 107 | public function with($isValid, array $properties = []) |
||
| 117 | } |
||
| 118 |
This check looks for PHPDoc comments describing methods or function parameters that do not exist on the corresponding method or function. It has, however, found a similar but not annotated parameter which might be a good fit.
Consider the following example. The parameter
$irelandis not defined by the methodfinale(...).The most likely cause is that the parameter was changed, but the annotation was not.