You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2023. It is now read-only.
All of the constructs need to be able to deal with hard deletion of nodes in the tree. Currently, the Directory API even has a deletedAt field which allows us to take soft deletions into account. the goal is to support soft deletes and appropriately portray this in the API.
This needs to be implemented in the following places:
All of the constructs need to be able to deal with hard deletion of nodes in the tree. Currently, the Directory API even has a
deletedAt
field which allows us to take soft deletions into account. the goal is to support soft deletes and appropriately portray this in the API.This needs to be implemented in the following places:
Sample user flow
Deletion
Directory A
). This will be an HTTP DELETE method.Directory B
andDirectory C
) with the given "deleted at" property.After deletion
Directory A
.Directory A
.Directory A
weren't deleted,Directory A
should remain effectively inaccessible.Directory A
.Directory B
.Directory A
's children.Caveats
The text was updated successfully, but these errors were encountered: