Should we try to migrate the legacy back-ported NodeTypeConstraints?

[mhsdesign]

Neos 8.3 contains findChildNodes as replacement for the deprecated getChildNodes

As seen here:
https://github.com/neos/neos-development-collection/blob/928cc4aa5b427b84cf18ae2af8578e916d0d3afb/Neos.ContentRepository/Classes/Eel/FlowQueryOperations/ChildrenOperation.php#L159

$node->getChildNodes('Neos.Neos:Document')

was replaced at some places with

$node->findChildNodes($this->nodeTypeConstraintFactory->parseFilterString('Neos.Neos:Document'))

im not sure if consumers really adapted to that but i have seen it around ^^

before we migrate anything here we should probably first migrate getChildNodes('Neos.Neos:Document') instead of the "newer" findChildNodes.

Fun really starts to begin with using complex filters with negation and comma: Neos.Neos:ContentCollection,Neos.Neos:Content,!Vendor.Site:Exclude

Additionally $limit = null and $offset = null might need to migrated as well if we find it worth. But the api changed see FindChildNodesFilter.

[dlubitz]

@mhsdesign Any news here?

[mhsdesign]

Okay updated the description. And also stated that its probably more worth to migrate getChildNodes('Neos.Neos:Document') than the backported - now removed - NodeTypeConstraintFactory ^^