-
-
Notifications
You must be signed in to change notification settings - Fork 223
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: #4614 NodeAggregateWasMoved change not marked as changed in correct dimension #5369
Closed
mhsdesign
wants to merge
1
commit into
neos:9.0
from
mhsdesign:bugfix/4614-node-move-not-marked-correctly-as-changed-in-dimension
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -214,21 +214,16 @@ private function whenNodeAggregateWasMoved(NodeAggregateWasMoved $event): void | |
return; | ||
} | ||
|
||
$affectedDimensionSpacePoints = iterator_to_array($event->succeedingSiblingsForCoverage->toDimensionSpacePointSet()); | ||
$arbitraryDimensionSpacePoint = reset($affectedDimensionSpacePoints); | ||
if ($arbitraryDimensionSpacePoint instanceof DimensionSpacePoint) { | ||
// always the case due to constraint enforcement (at least one DSP is selected and must have a succeeding sibling or null) | ||
|
||
// WORKAROUND: we simply use the event's first DSP here as the origin dimension space point. | ||
// But this DSP is not necessarily occupied. | ||
// @todo properly handle this by storing the necessary information in the projection | ||
|
||
$this->markAsMoved( | ||
$event->getContentStreamId(), | ||
$event->getNodeAggregateId(), | ||
OriginDimensionSpacePoint::fromDimensionSpacePoint($arbitraryDimensionSpacePoint) | ||
); | ||
} | ||
// WORKAROUND: we simply use the event's DSP here as the origin dimension space point. | ||
// But this DSP is not necessarily occupied. | ||
// @todo properly handle this by storing the necessary information in the projection | ||
// todo so we need to create a change if there is none???? | ||
Comment on lines
+217
to
+220
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this will start to bite us with #5314 in place as scatter will be started to be used: But i wonder if that is not already handled via modifyChange? I guess a test could answer that ... |
||
|
||
$this->markAsMoved( | ||
$event->getContentStreamId(), | ||
$event->getNodeAggregateId(), | ||
OriginDimensionSpacePoint::fromDimensionSpacePoint($event->dimensionSpacePoint) | ||
); | ||
} | ||
|
||
private function whenNodePropertiesWereSet(NodePropertiesWereSet $event): void | ||
|
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so that we need the originally attempted dimensionSpacePoint to be moved seems correct. But the question is, see #5360 if also the relationDistributionStrategy should be part of the event?
Whas is your opinion? @nezaniel
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it wouldn't hurt to have the strategy in here if only for potential debugging help....