BUG: Fluid templates using Nodes might certainly become impossible out of the box with Neos 9

[mhsdesign]

... because we lack the corresponding eel helpers.

Currently we ship some Neos.Node helpers which replace field access that was previously directly accessible on the Node (in 8.3)

class NodeHelper
{
    public function label(Node $node): string;
    public function depth(Node $node): int;
    public function path(Node $node): string;
    public function nodeType(Node $node): ?NodeType;
    public function isOfType(Node $node, string $nodeType): bool;
    public function isDisabled(Node $node): bool;
}

We are conceptualising a translation layer, which would be made for EEL and would require a total different implementation for Fluid: #5022
(Fluid has an extension point that we can leverage, the question is how much work are we willing to put into this to make the Neos\FluidAdaptor\Core\ViewHelper\TemplateVariableContainer have special handling for nodes?)

With the recent prs (#5020) and (#5021) fluid will not only have to adjust to node.identifier not working anymore but also node.nodeType and node.label. This also affects ourselves in templates like these:

neos-development-collection/Neos.Neos/Resources/Private/Partials/Module/Management/Workspaces/ContentChangeDiff.html

Lines 8 to 10 in 023a2fe

	<i class="{change.configuration.ui.icon}" title="{f:if(condition: change.node.nodeType.label, then: '{neos:backend.translate(id: change.node.nodeType.label)}', else: '{change.node.nodeType.name}')}" data-neos-toggle="tooltip"></i>
	</f:if>
	{change.node.label}

The price question is are we okay with Fluid integration not being a viable option anymore with Neos 9?
As long as Fluid only works with primitive types and the integration is done in Fusion, this will not be a problem, but anything further than this will be hard.

Also this affects custom backend modules as well as they might operate on nodes where we have no rector migration in place nor a translation layer.

Additionally there is a big regression in Fluid since 9.0 regarding Neos.Fusion:Template's attributes now being an array:
#4885

And last but not least with #4654 the pages default body is changed too and no longer a template. If we want to continue supporting fluid we should provide a guide how to reset to 8.3 behaviour.

So as far as i see it if we dont put some love into this fluid will be dead with Neos 9 and just a cosmetic dependency.

[mhsdesign]

To repair our backend module templates we would probably need to introduce a NodeInformation view helper or something, to get the nodetype and the label by node?

[ahaeslich]

To repair our backend module templates we would probably need to introduce a NodeInformation view helper or something, to get the nodetype and the label by node?

After converting the workspace module to react + fusion (see: #4255) ... which fluid templates would need to be adjusted?

[mhsdesign]

usages:

node.nodeType

• Neos.Media.Browser/Resources/Private/Templates/Usage
  • RelatedNodes.html
• Neos.Neos/Resources/Private/Partials/Module/Management/Workspaces
  • ContentChangeDiff.html
• Neos.Neos/Resources/Private/Partials/Module/Shared
  • DocumentBreadcrumb.html
• Neos.Neos/Resources/Private/Templates/Service/Nodes
  • Index.html
  • Show.html

node.label

• Neos.Media.Browser/Resources/Private/Templates/Usage
  • RelatedNodes.html
• Neos.Neos/Resources/Private/Partials/Module/Management/Workspaces
  • ContentChangeDiff.html
• Neos.Neos/Resources/Private/Templates/Service/Nodes
  • Index.html
  • Show.html

[mhsdesign]

beyond that fluid might currently work not at all? https://neos-project.slack.com/archives/C04PYL8H3/p1716467391919169

[mhsdesign]

The Nodes controller and fluid is probably responsible for rendering the referenceable nodes in the reference editor. Due to node.label not working it will not work as expected. See slack.