Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUGFIX: 3574 initialize foreign referenced nodes #3576

Merged
merged 2 commits into from
Aug 28, 2023

Conversation

mhsdesign
Copy link
Member

@mhsdesign mhsdesign commented Jul 10, 2023

resolves: #3574

actual fix instead of hotfix: #3575 and neos/neos-development-collection#4399

similar to @grebaldi solution at: #3364

What I did

How I did it

How to verify it

revert: neos/neos-development-collection#4399 and try to follow #3574

@github-actions github-actions bot added Bug Label to mark the change as bugfix 7.3 labels Jul 10, 2023
@Sebobo
Copy link
Member

Sebobo commented Jul 10, 2023

Should we go with both PRs just to be one the safe side?

@mhsdesign
Copy link
Member Author

No I rather not - I like to be more explicit and if we just ignore any unexpected input wrong behaviour will later be worse to debug then if there was an exception.

we can still write a safeguard and log an error to the console if you want…

@Sebobo
Copy link
Member

Sebobo commented Jul 10, 2023

Yes then I will adjust my PR to do that. The code there just relies too much on data being there.

Copy link
Contributor

@dlubitz dlubitz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like! ❤️ I can't evaluate the technical solution, but it looks reasonable.

Copy link
Contributor

@grebaldi grebaldi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM code-wise.

However, I was unable to reproduce the issue as per description in #3574.

packages/neos-ui/src/manifest.js Outdated Show resolved Hide resolved
@mhsdesign
Copy link
Member Author

However, I was unable to reproduce the issue as per description in #3574.

Maybe because we have the hotfix #3575 already merged? (So the console output should still complain, but less so)

Also for future reviewers: Make sure to revert neos/neos-development-collection#4399 once its merged ;)

@grebaldi
Copy link
Contributor

@mhsdesign

Maybe because we have the hotfix #3575 already merged? (So the console output should still complain, but less so)

Oh yes, didn't see that :)

Co-authored-by: Wilhelm Behncke <2522299+grebaldi@users.noreply.github.com>
@mhsdesign mhsdesign merged commit 5b3fa1d into 7.3 Aug 28, 2023
5 checks passed
@mhsdesign mhsdesign deleted the bugfix/3574-fetch-foreign-referenced-nodes branch August 28, 2023 12:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
7.3 Bug Label to mark the change as bugfix next-patch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BUG: Neos UI crashes after applying references with Neos.NodeTypes.ContentReferences:ContentReferences
4 participants