Closed johannessteu closed 4 months ago
@johannessteu the interesting question would be when do you have a TraversableNodeInterface that is not a NodeInterface (thus going into the first condition) in 8.3?
Hey @kitsunet 👋🏻 I actually didn't dig too deep into it yet, was adding that fusion code to https://github.com/networkteam/Networkteam.Neos.ContentApi#extending-api-site-properties as i'm testing the next integration right now. Wondering if it's then an issue with this custom rendering there 🤔
Jup i think we can close this as wont fix. Neither the current Node
nor the NodeInterface
or the TraversableNodeInterface
will survive 9.0
In parts it looks like one can implement a custom node by implementing only the TraversableNodeInterface
but this is not true. If you do anything unexpected (probably hacky) you have to extend the whole Node
to make sure everything works.
So the check against TraversableNodeInterface
was made as forward compatible idea but we were on the wrong track.
Is there an existing issue for this?
Current Behavior
The CachingHelper is using
$node->getContentStreamIdentifier()
here. This method is no longer supported on~8.3.0
and fails with anNodeMethodIsUnsupported
exceptionExpected Behavior
CachingHelper should not fail at all
Steps To Reproduce
Fusion:
Environment
Anything else?
No response