List of advanced things that cannot be migrated automatically

[mhsdesign]

• Custom importers or other code which create nodes in the Content Repository
• Anything that touches the write-side of the CR
• Custom frontend routing, extending / replacing the FrontendNodeRoutePartHandlerInterface
• Relying on low-level / internal parts like the NodeDataRepository, NodeData or Workspace doctrine entity
• Signal-Slot pattern usage
• Custom CR Security Privileges

Flow things

• neos/behat refactoring !!! TASK: Radical cleanup behat#35
• flows view-interface change

More specific things

• Node::createNodeFromTemplate -> provide runtime helper??
• creating a content-context out of thing air with sane defaults, as there is no official default dimension space point config, or is there?: Discussion: Default dimension / default context in the new CR neos-development-collection#5113
• get the siteNode by site entity (and reverse)

$siteNode = $subgraph->findNodeByPath(
   $siteInstance->getNodeName()->toNodeName(),
   $subgraph->findRootNodeByType(NodeTypeNameFactory::forSites())->nodeAggregateId
);

• how to use cr in CLI, pass Neos site node name, use $siteRepository->findDefault() or pass --content-repository (which is default by default)
• how to deal with complexity of multiple crs? Encapsulate CR as constructor param or continue working with Flow/Singleton and pass the $cr all the way through, or just pass the $node and refetch the $cr all the time via registry?
• how to deal with nodes not being an active record anymore? What if i depend on that it changes everywhere?
• How to serialize a node to the frontend and have a controller accept it again?
• Pass Node around vs NodeAddress vs Subgraph or yet again a subgraph identity see comment

See also

• Which are the parts of my Neos project that will most likely need to be reimplemented when upgrading? in https://www.neos.io/blog/neos-9-0-masterplan.html
• List of (integration) Fusion, Yaml etc things that cannot be easily migrated automatically #67