Adjust to changed CR NodeType fallback handling #178
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ahaeslich
force-pushed
the
nodeTypeFallbackHandling
branch
from
38e36c4 to
4659736
Compare
ahaeslich
approved these changes
Oct 8, 2023
There was a problem hiding this comment.
Updated based on changes in neos/neos-development-collection#4466
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adjusts NodeType fallback handling to the latest CR changes.
Background: The NodeTypeManager no longer does fallback handling but throws an exception instead. The fallback handling mechanism has been moved to Neos.Neos, which provides a utility trait to deal with this.
Should be merged AFTER neos/neos-development-collection#4466