Context
Vault-Web/cloud-page#79 adds a per-user trash (soft delete) on the backend: DELETE /files now moves a file into a per-user trash instead of deleting it permanently, plus new endpoints under /files/trash to list, restore, and permanently delete entries. Expired entries are auto-purged after 30 days.
This is not yet visible in the vault-web frontend — the cloud view has no way to view or manage trashed files, so the feature has no user-facing effect until it is wired up.
Goal
Add a trash view to the cloud page that consumes the new endpoints.
New backend endpoints (from cloud-page#79)
GET /files/trash — list entries (id, name, originalPath, deletedAt, size)
POST /files/trash/{id}/restore — restore to original path
DELETE /files/trash/{id} — permanently delete
Tasks
References
Context
Vault-Web/cloud-page#79 adds a per-user trash (soft delete) on the backend:
DELETE /filesnow moves a file into a per-user trash instead of deleting it permanently, plus new endpoints under/files/trashto list, restore, and permanently delete entries. Expired entries are auto-purged after 30 days.This is not yet visible in the vault-web frontend — the cloud view has no way to view or manage trashed files, so the feature has no user-facing effect until it is wired up.
Goal
Add a trash view to the cloud page that consumes the new endpoints.
New backend endpoints (from cloud-page#79)
GET /files/trash— list entries (id,name,originalPath,deletedAt,size)POST /files/trash/{id}/restore— restore to original pathDELETE /files/trash/{id}— permanently deleteTasks
CloudService(frontend/src/app/services/cloud.service.ts) for the three endpointsTrashEntrymodel (id,name,originalPath,deletedAt,size)References