Feature/add node tree function #514
Closed
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
electronicbites
force-pushed
the
feature/add-node-tree-function
branch
from
0fa5da4
to
709b7c8
Compare
electronicbites
force-pushed
the
feature/add-node-tree-function
branch
3 times, most recently
from
739fc12
to
e566691
Compare
electronicbites
force-pushed
the
feature/add-node-tree-function
branch
from
e566691
to
1bd0a00
Compare
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.
As a preparation for moving nodes I implemented a function to return the whole outline tree of an episode with the help of a recursive common table expression. It does not load the associations
prevandparent, I could not find a way how this could work without loading single nodes multiple times. Instead I introduced a virtual attributelevelthat should help to work with changing nodes in the tree.This is draft since I would like to implement the move_node function which uses this tree function. So there might be changes, or at worst it turns out this as it is wont work well.
So this is a sneak preview of the tree function as I intended to implement it and gives you the chance to raise your concerns ;)