BUGFIX: Proper error if site node not found in backend #3954
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.
It seems the (internal) contract for providing the UI state requires no site or document node, but this is not true (obviously)
The
defaultNodesForBackend
helper will just crash:It is invoked here via YAML - hence we did not detect this null pointer bug:
neos-ui/Configuration/Settings.yaml
Line 131 in ebed351
Instead now a pretty error is throw which will also highlight probably its cause:
In my case i had a configuration laying around adding a new dimension
targetGroup
for all sites which was un nice which lead to no nodes being found.