[Neos] Why not to subclass TYPO3.Neos:ContentCollection?
aske at moc.net
Sat Mar 22 18:18:07 CET 2014
I remember Rens talking about this being something that's not supported as it is now. We'll definitely need this to make the DOM more flexible for things like grid frameworks, but it's still something that has to be worked on.
On Feb 7, 2014, at 4:13 AM, Marcin Ryzycki <marcin at ryzycki.com> wrote:
> On 2014-01-24 02:07:43 pm +0000, Christian Müller said:
>>> In NodeTypes.yaml inside TYPO3.Neos package it's stated:
>>> # Cannot be subclassed.
>> Might be that we need to evaluate that again. Shortly before the 1.0 release the ContentCollection rendering was heavily modified, it could be the case that before something was hardcoded that no longer is hardcoded now. I will try to follow up with that and find out if the comment can be removed.
> Hi Christian,
> I actually didn't follow up with that - there are some issues there.
> Basically, when you extend TYPO3.Neos:ContentCollection it works in terms of rendering properly collection of nodes inside.
> Uncaught RangeError: Maximum call stack size exceeded in ext-direct.js.
> Seems like encodeString() is called in infinite loop. The error is the same if you add some properties directly to TYPO3.Neos:ContentCollection - so it actually doesn't matter if it's subclassed or not.
> I did dummy package with an example for that if you'd like to follow up:
> Neos mailing list
> Neos at lists.typo3.org
More information about the Neos