Overview of merged pull requests¶
The UI package comes with a new image serializer that needs to be configured so the test sees it’s expected result.
This change depends on [1b4562c8b71a595b48fec03fac9cd52b9f8c7a5e](https://github.com/neos/neos-ui/pull/1866/commits/1b4562c8b71a595b48fec03fac9cd52b9f8c7a5e) in the UI package.
- [ x] The PR is created against the [lowest maintained branch](https://www.neos.io/features/release-roadmap.html)
See discussion there for more details.
This PR adds documentation regarding the ability to disable Editors, which is added in this PR: https://github.com/neos/neos-ui/pull/1665
Added a filtering for movedTo like we already do in filterNodeDataByBestMatchInContext.
See description of the discovered behavior in https://github.com/neos/neos-ui/issues/1523#issuecomment-379247165.
Dynamic cache entries are complex and need a lot of information to be evaluated correctly, therefore the runtime should always take care of this. This is potentially a bit slower than the original code but definitely more correct in outcome. Before tags were definitely wrong as they were based on the parent elements configuration.
When the context of the “resolved” node does not have a “current” site in LinkingService.createNodeUri() a fatal error was triggered. This adds a check and handles the case like a site node path mismatch.
Since we overwrite the logoutAction from Flow, we need to annotate it with @Flow\SkipCsrfProtection here too.
When checking for missing child nodes it doesn’t check if the existing child nodes are the correct node type. This can happen when a node has been changed to the fallback node type or if the child node type is changed in the configuration.