feat: Change Tree Sortindex call#56
Open
ArneGudermann wants to merge 1 commit into
Open
Conversation
Member
|
I'm not convinced this change is the right direction. The viur-core already provides an explicit move operation that correctly handles relocating nodes including their entire subtrees. Switching to edit here seems to bypass that intended mechanism and could introduce inconsistencies, especially regarding hierarchical integrity. Could you clarify the rationale behind replacing move with edit in this context? From a design perspective, it would be preferable to rely on the dedicated operation that semantically represents the action being performed. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.