jorrit Not sure if it has to do with your extension, but since some time I get warnings like this: ... and ...
JakubMisek jorrit, this is usually caused when using some laravel stub generators, which create invalid code. From the sample provided, I'm not able to give any help. How is the $workorder created? Can you track where stdclass is coming from?
jorrit You can close this thread. As sudden as it appeared, as sudden it disappeared like a week later.
jorrit Hi Jakub, the issue still occurs. In the screenshot below you can see more about the cause. The array comes from a regular Laravel Eloquent Builder query. The mouseover hints two return types, but within the foreach loop only the latter is used, so it seems, because $workorder is considered to be a StdClass, as you can see in the second image of my first post.
JakubMisek jorrit, Hi Jorrit, Thank you for the update; I have successfully replicated the issue with a minimal test case: I'm not sure why Illuminate\Database\Query\Builder::get() returns Collection of stdClass, but we should respect both results in the foreach loop - will be fixed!
