dimaip
(Dmitri Pisarev)
December 2, 2015, 10:21am
1
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
aertmann
(Aske Ertmann)
December 2, 2015, 10:46am
2
Sounds like a good idea to me. Originally proposed the history API was based on them as well, but didn’t happen though.
dimaip
(Dmitri Pisarev)
December 2, 2015, 11:44am
3
What about setting node context variable? How do I create Node from NodeData?
With createContextMatchingNodeData
and createFromNodeData
?
christianm
(Christian Müller)
December 2, 2015, 4:02pm
4
There is no Context, you cannot have a Node there. This is low level.
But generally EEL might make sense yes.
christianm
(Christian Müller)
December 2, 2015, 4:03pm
5
Ah and so no documentNode and site, because they are only relevant in a Neos context, but the migrations are a CR service.
dimaip
(Dmitri Pisarev)
December 2, 2015, 7:01pm
6
1 Like