Repository navigation
feat: plan the removal of a data entity - #26
Merged
Merged
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
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.
Adds a planned removal of one data entity from a crate, so Aruna can let plugins and users remove a file entry from a dataset's metadata.
CraqleNode::plan_remove_dataplans the removal of one root-linkedFileentity (also stored asMediaObject): every triple it holds and the root'shasPartlink to it. Other subjects and their references to it stay.#contextual entities and non-file entities are refused without a change.hasPartlink again under their new dot, so an edit made concurrently with a removal keeps the entity whole.