TASK: Add node states isCreated, isModified and isRemoved to TreeNode
#3962
Conversation
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
mficzel
force-pushed
the
feature/add-change-state-to-tree-endpoints
branch
7 times, most recently
from
2300df2 to
2db5b71
Compare
mficzel
changed the title
isCreated, isModified and isRemoved to TreeNode
mficzel
force-pushed
the
feature/add-change-state-to-tree-endpoints
branch
from
2db5b71 to
391ea4c
Compare
…to TreeNode The information is obtained from the pendingChangeProjection nodes that are removed but not yet published in the current workspace will still show up but not their children that only inherited the removed tag and have no change pending.
mficzel
force-pushed
the
feature/add-change-state-to-tree-endpoints
branch
from
391ea4c to
92890af
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.
Add node state information isCreated, isModified and isRemoved to TreeNode
The information is obtained from the pendingChangeProjection nodes that are removed but not yet published
in the current workspace will still show up but not their children that only inherited the removed tag and have no change pending.
How I did it
Basically the nodes are read without subtree tag constraints but all removed nodes are filtered out if they
inherited the removed tag or have no pending change with deleted so they were deleted in another workspace.