Feature: "Cancel" newly-created unsaved node/edge removes it #110
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.
Addresses #53
If you create a new node, then change your mind and decide to cancel the creation, the new node will be deleted. (When the user clicks "New Node", a node is immediately created and saved. Prior to this, clicking "Cancel" would leave the newly created node in place).
Similarly, if you create a new edge, then change your mind and decide to cancel the creation, the new edge will be deleted.
ADDITIONAL NOTES:
Revision
field. We make use of this to decide whether to delete a "Canceled" node/edge. Upon creation, a new node/edge has a revision value of-1
. When you save the node/edge the revision is incremented to 0. If you "Cancel" a node or edge edit and the revision is still at-1
, we delete the node or edge.Created
andUpdated
fields. Prior to this they were left blank.