Add Rename to the office file list #151

New issue

Open

opened 2026-04-26 08:19:03 +00:00 by zaelgohary · 0 comments

zaelgohary commented

2026-04-26 08:19:03 +00:00

Member

FileListView exposes Upload and Delete; there is no Rename. Standard expectation for a file manager UI.

Acceptance

A Rename action on each FileRow (button or right-click) opens a small inline editor for the filename.
Submission calls a new service::rename_file(old, new) that PUTs/MOVEs through the hero_foundry REST API (MOVE per WebDAV, or DELETE + PUT if that's what the API supports).
Doc_key derivation (context + filename + mtime) means the renamed file gets a fresh key — confirm an open editor session for the old name closes cleanly or refreshes.
Reject collision (renaming to an existing filename) with a clear inline error.

`FileListView` exposes Upload and Delete; there is no Rename. Standard expectation for a file manager UI. ## Acceptance - A Rename action on each `FileRow` (button or right-click) opens a small inline editor for the filename. - Submission calls a new `service::rename_file(old, new)` that PUTs/MOVEs through the hero_foundry REST API (`MOVE` per WebDAV, or DELETE + PUT if that's what the API supports). - Doc_key derivation (`context + filename + mtime`) means the renamed file gets a fresh key — confirm an open editor session for the old name closes cleanly or refreshes. - Reject collision (renaming to an existing filename) with a clear inline error.