Closed mwjames closed 5 years ago
Not enough info to tell if this issue is wit ParamProcessor or the caller.
As with https://github.com/JeroenDeDauw/ParamProcessor/issues/36 it seems like a parameter value is an array at a point where it should not be. Perhaps the calling code is incorrectly assuming it can provide an array where it should be providing a string?
Not enough info to tell if this issue is wit ParamProcessor or the caller.
I'm fairly aware of that and I said I found that in the PHP log so I don't know the context but I thought I'm a good sport and create a report instead of just ignoring it.
Feel free to ignore it, close it, or deal with it as you see fit.
On 9/23/18, Jeroen De Dauw notifications@github.com wrote:
Not enough info to tell if this issue is wit ParamProcessor or the caller.
As with https://github.com/JeroenDeDauw/ParamProcessor/issues/36 it seems like a parameter value is an array at a point where it should not be. Perhaps the calling code is incorrectly assuming it can provide an array where it should be providing a string?
-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/JeroenDeDauw/ParamProcessor/issues/37#issuecomment-423788445
param-processor/param-processor: 1.3.4
PHP log has reports of: