Closed mwjames closed 8 years ago
Do you know if this issue occurs with the latest version of this library? Bugfixes where made since 1.2.2
Do you know if this issue occurs with the latest version of this library? Bugfixes where made since 1.2.2
Lines are different [0], code is the same $values = $param->getValue();
. I'm guessing getValue
doesn't return an expected array and that is why foreach ( $values as &$value )
complains about it.
No other stack trace, no hint as the where and by what it is caused, it just appeared during the refreshLinks.php
run.
[0] https://github.com/JeroenDeDauw/ParamProcessor/blob/master/src/ParamDefinition.php#L482-L486
According to [0] $param->getValue();
returns a mixed type, so no guarantee for an array.
[0] https://github.com/JeroenDeDauw/ParamProcessor/blob/master/src/Param.php#L462-L469
Yeah sure, no guarantee, though if isList
returns true, it really ought to be. Probably null or something. Will investigate.
I looked at this for 20 minutes and did not find the source. It is very possible the error is coming from code using ParamProcessor and simply not caught until this point. Hard to tell, very high code complexity and little encapsulation
Just run into it while researching something else.
param-processor/param-processor 1.2.2