byjg /
anydataset
| 1 | <?php |
||
| 8 | class FixedTextDefinition |
||
| 9 | { |
||
| 10 | |||
| 11 | public $fieldName; |
||
| 12 | public $startPos; |
||
| 13 | public $length; |
||
| 14 | public $requiredValue; |
||
| 15 | public $subTypes = array(); |
||
| 16 | |||
| 17 | /** |
||
| 18 | * |
||
| 19 | * @param string $fieldName |
||
| 20 | * @param int $startPos |
||
| 21 | * @param int $length |
||
| 22 | * @param bool|string $requiredValue |
||
| 23 | * @param FixedTextDefinition[] $subTypes |
||
| 24 | */ |
||
| 25 | 2 | public function __construct($fieldName, $startPos, $length, $requiredValue = "", $subTypes = null) |
|
| 33 | } |
||
| 34 |
Our type inference engine has found an assignment of a scalar value (like a string, an integer or null) to a property which is an array.
Either this assignment is in error or the assigned type should be added to the documentation/type hint for that property.
To type hint that a parameter can be either an array or null, you can set a type hint of array and a default value of null. The PHP interpreter will then accept both an array or null for that parameter.
The function can be called with either null or an array for the parameter
$needlebut will only accept an array as$haystack.