TYPO3 Core

The "Cleanup ClassLoader" task #56797 removed a try/catch-Block which caught this exception previously.

Helmut Hummel wrote:

Christian Weiske wrote:

Steps to reproduce:

1. Extbase controller:

$this->view->assign('foo', '1:2');

2. Fluid template:

<if condition="{foo.bar}"></if>

could not trigger this with this code (class loader is not triggered with class name "1:2")

Ah, OK, could reproduce it now.
Can you provide a real use case where this can happen?

$this->view->assign('foo', '1:2'); and then <if condition="{foo.bar}"></if> is not nice to fatal there (which is fixed now btw), but it also does not look like it makes much sense to do things like that ;)

Anyway, if we can avoid triggering the class loader in Fluid, we should do so. For that we need to understand the use case and how we then can deal with that in Fluid

We have some partials that used to render generic data elements.

For example:

$data[] = (object)array('value' => 12.5, 'unit' => 'C');
$data[] = '12:05';

Those data are aggregated from different APIs.

Now our partial contains the following code to determine if it is a unit/value datum or not:

<if condition="{datum.value}">
 <then>{datum.value} {datum.unit}</then>
 <else>{datum}</else>
</if>

I think this is a sensible use case.

Christian Weiske wrote:

We have some partials that used to render generic data elements.

Those data are aggregated from different APIs.
Now our partial contains the following code to determine if it is a unit/value datum or not:

Thanks.

I think this is a sensible use case.

Absolutely! I pushed a patchset to prevent the lookup if the subject is a scalar (neither array nor object)