Example of old usages:

@process.augment = Neos.Fusion:Augmenter {
  id = ${node.identifier}
}

@process.augment = Neos.Fusion:Augmenter {
  id = ${node.nodeAggregateIdentifier}
}

Example of usage in Neos 9:

@process.augment = Neos.Fusion:Augmenter {
  id = ${node.nodeAggregateId.value}
}

• It will generate comments for lines that are using flow query operations like parent() or parents()
• The comment says You may need to rewrite "VARIABLE.parent" to Neos.NodeAccess.findParent(VARIABLE). But I found no matching eel helper.

• migrate node.context.currentSite to eel helper to fetch site entity
• migrate node.context.workspace to eel helper to fetch workspace, but attention, the workspace api in fusion also changed.
• warn if anything else is accessed by node.context.*
• while the renderingMode has a basic migration via #22, but the not all things are migrated currently
  • node.context.workspace.name == 'live' -> !renderingMode.isEdit
  • node.context.workspace.personalWorkspace -> renderingMode.isEdit
  • node.context.currentRenderingMode.* -> renderingMode.*

For example I got this exception while updating a project (DocsNeosIo) to Neos9:

Required class "Neos\ContentRepository\Migration\Transformations\AbstractTransformation" could not be loaded properly for reflection from "Neos\DocsNeosIo\ContentRepository\Transformations\UpdateHyphenTransformation"

And I know a fix for all classes will not be possible/overwhelming, but at least the most used ones should be fixed/commented by rector

Resolves partly neos/neos-development-collection#4396

As @mficzel said here neos/neos-ui#3571:

replace Neos.Node.inBackend(node) which is removed here neos/neos-development-collection#4067 with Neos.Backend.isEditMode(request) || Neos.Backend.isPreviewMode(request)

Currently node.context.inBackend is rewritten to Neos.Node.inBackend, but we might get rid of that method or deprecate it...

The question is if we should provide a Flow or rector migration for existing 9.0 projects using Neos.Node.inBackend? - could be a simple regex ^^ (or one needs to run this regex yourself via php storm.)

search

Neos.Node.inBackend\([a-zA-Z]*\)

replace with

Neos.Backend.isEditMode(request) || Neos.Backend.isPreviewMode(request)

On the Neos Sprint in Hamburg I found out that some signals have been removed and replaced with catchUpHooks.

It would be pretty awesome if it would be possible to get a comment if the used signal is no longer supported
Maybe with a small hint for the hooks

We should provide a migration for people using „sites“ and rewrite this to Neos.Neos:Sites

Originally posted by @mhsdesign in neos/neos-development-collection#4339 (comment)

to be discussed in which places this should happen.

most obvious ones are in yaml configurations fx for startingPoints of the reference editor.

i think transforming php automagically might not be trivial, so I would count on manual migration there, but we should still highlight possible places with todo comments

See: neos/neos-development-collection#4520

the NodeTypeManager can provide replacements:

- $nodeType->getAutoCreatedChildNodes();
+ $nodeTypeManager->getTetheredNodesConfigurationForNodeType($nodeType);

- $nodeType->hasAutoCreatedChildNode($nodeName);
+ $nodeType->hasTetheredNode($nodeName);

- $parentsNodeType->getTypeOfAutoCreatedChildNode($nodeName);
+ $nodeTypeManager->getTypeOfTetheredNode($parentsNodeType, $nodeName);

- $grandParentsNodeType->allowsGrandchildNodeType($parentNodeName, $nodeType);
+ $nodeTypeManager->isNodeTypeAllowedAsChildToTetheredNode($grandParentsNodeType, NodeName::fromString($parentNodeName), $nodeType);

_hiddenAfterDateTime => disableAfterDateTime
_hiddenBeforeDateTime => enableAfterDateTime

These prototypes are not longer a part of neos after the Update to version 9

The correct prototype in this case would be Neos.Fusion:DataStructure as far as I found out

• NodeType::getName was removed neos/neos-development-collection#4560
  • migrate ${node.nodeType.name} to ${node.nodeTypeName.value} (not 100% equivalent but should mostly do)
  • migrate $nodeType->getName() to $nodeType->name->value
• #33
• #34
• #31
• #29
• #35
• #41

neos/neos-development-collection#5020

Following code should be migrated:

- $node->getNodeTypeName();
+ $node->nodeTypeName;

- $node->getNodeType()->getName();
+ $node->nodeTypeName->value;

- $nodeType->getName();
+ $nodeType->name->value;

- $node->getNodeType();
+ $nodeTypeManger = ...;
+ $nodeTypeManager->getNodeType($node->nodeTypeName);

- $node->getNodeType()->getTypeOfAutoCreatedChildNode(NodeName::fromString('name'));
+ $nodeTypeManager->getTypeOfTetheredNode($node->nodeTypeName, NodeName::fromString('name'));

In neos/neos-development-collection#4555 (comment) we removed the NodeSearchService. There was also a discussion about re-adding the Service, but was decided against: neos/neos-development-collection#3771

There are Upgrade instructions in the PR to migrate, but we should think about adding a comment or hint directly using rector.

... to be defined and discussed if deemed useful.

node.context is not available anymore.

https://github.com/neos/neos-development-collection/blob/f4ed8369957209ba689cb2e1d9319e39716d6ac3/Neos.Neos/Resources/Private/Fusion/Prototypes/ContentCollection.fusion#L30

... because we use an outdated rector version and also the pin on phpstan will prohibit any other version installed.
This is unfortunate and ideally we should upgrade to rector stable 1.x from our current 0.15.8 from april 23. The upgrade is not straight forward due to many breaking changes, which also happened in patch levels (they dont do semver) #56.
As discussed in the weekly our last resort would be to just bundle a phar and have that installed and at a later point totally refactor this package, removing all previous rules.

cc @kitsunet @dlubitz @ahaeslich