Bubble up delete functionality - #35
Merged
Merged
Conversation
MattToast
approved these changes
Aug 21, 2026
MattToast
left a comment
MattToast
left a comment
Collaborator
There was a problem hiding this comment.
LGTM!! Thanks for the added functionality!!
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.
Allows keys (both blob and metadata) to be deleted using both backends. This uses the delete methods on both Clients and the OutgoingHandle to ensure that both keys associated with a given item are deleted. This is restricted to OutgoingHandle deliberately under the the principle that the producer of an item should only be able to remove it.