Marc Henry Schultz
Marc Henry Schultz
Also when enums get deleted they seem to crash the compilation of flow because `unserialize`: ``` 22 Neos\Flow\Error\ErrorHandler::handleError(2, "unserialize(): Class 'Neos\ContentRepository\Core\…eRebase\Dto\RebaseErrorHandlingStrategy' not found", "/Users/marchenryschultz/Code/core/neos-manufacture…k/Neos.Cache/Classes/Frontend/VariableFrontend.php", 94) 21 unserialize("a:4:{s:19:"classReflectionData";a:1775:{s:11:"Arra…e";a:1:{s:11:"onPostFlush";s:11:"onPostFlush";}}}}") 20 Neos\Cache\Frontend\VariableFrontend::get("ReflectionData") 19...
Also our `ContentSubgraphWithRuntimeCaches` can be improved a lot as it mostly doenst cache or read from the cache. I found a tiny improvement here already: https://github.com/neos/contentrepository-development-collection/pull/129
discussions we had on the 4.7.25. regarding neos 9 cr optimisation: - explict workspace creation screen - the user will see that the login worked and see neos fast -...
### regarding legacy `invisibleContentShown`: Regarding `includeInvisible([])` we should definitely use the `disabled` naming here (https://github.com/neos/neos-development-collection/issues/4312) and we actually prepared with the introduction of subtree tags new possibilities than just disabled...
https://github.com/neos/neos-development-collection/pull/5130 would reintroduce the 8.3 syntax for workspaceName, dimensions, invisibleContentShown (untested yet)
As i wrote > The context operation should thus not be seen as forever-staying feature and will likely be deprecated and replaced with more explicit ways which fit better the...
I agree with @bwaidelich and share the concern that the synchronous option will sneak as "performance improvement" into client code and other packages as well. Currently speeding up the catchup...
Also related, during the discussion of exposing the workspace name in the node we considered the idea of virtual workspace names: > WorkspaceName::fromString() must be stricter without colons (so that...
im still confused what the reason for the `search` operation is in general but it seems to be used via javascript: https://github.com/neos/neos-ui/blob/9e47fdfd4d8ef345f75cf88ce34c178c0b161637/packages/neos-ui-sagas/src/UI/PageTree/index.js#L163
> FusionCachingAspect is gone with #3839 ;)