RFC: parse transformation's settings with EEL

I think it would give a lot more flexibility, if the settings array of transformation was parsed with EEL.
node, documentNode and site should be available as context variables. The problem is that transformations operate on NodeData, and not Node, so the questions is in what context those context variables be set?

This would be very useful in things like actions on node creation: https://github.com/neos/neos-development-collection/pull/205

Sounds like a good idea to me. Originally proposed the history API was based on them as well, but didn’t happen though.

What about setting node context variable? How do I create Node from NodeData?
With createContextMatchingNodeData and createFromNodeData?

There is no Context, you cannot have a Node there. This is low level.
But generally EEL might make sense yes.

Ah and so no documentNode and site, because they are only relevant in a Neos context, but the migrations are a CR service.

Ok, done it as part of actions PR: https://github.com/dimaip/neos-development-collection/commit/4feb7ff0c0e0498f191f79157dc809e8da419a56
Will add tests and documentation tomorrow.

1 Like