[Feature] Drag-and-drop upload onto file spaces and folders #32

Open
opened 2026-07-14 20:08:43 +02:00 by zemion · 1 comment
Owner

Problem / User Need

Users should be able to upload by dragging files directly onto a file space or folder, not only through a dedicated upload control.

Acceptance Criteria

  • Dropping files onto a managed file space uploads them to that space root or current folder.
  • Dropping files onto a folder uploads them into that folder.
  • Drop targets provide visual feedback before drop.
  • Permissions and connector/write-policy restrictions are enforced before accepting drops.
## Problem / User Need Users should be able to upload by dragging files directly onto a file space or folder, not only through a dedicated upload control. ## Acceptance Criteria - Dropping files onto a managed file space uploads them to that space root or current folder. - Dropping files onto a folder uploads them into that folder. - Drop targets provide visual feedback before drop. - Permissions and connector/write-policy restrictions are enforced before accepting drops.
Author
Owner

Codex State: progress

Summary

  • Local Core commit b5cfba6 resolves browser drops explicitly, adds drag-state feedback and readable disabled/empty/unreadable rejection paths, and tests directory/file extraction.
  • Local Files commit 8c5f149 routes each drop to the concrete file-space/folder target, covers the current-folder surface, and refuses permission-denied, busy, missing, or connector targets with an explanation.

Verification

  • Core: npm run test:file-drop-zone (passed)
  • Files: npm run test:file-drop-target (passed)
  • Core WebUI production build (passed)

Next / Blocked

  • Keep open until the local commits are reviewed/integrated; then verify the server-side connector/write-policy response in the integrated UI and close if no gap remains.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Local Core commit b5cfba6 resolves browser drops explicitly, adds drag-state feedback and readable disabled/empty/unreadable rejection paths, and tests directory/file extraction. - Local Files commit 8c5f149 routes each drop to the concrete file-space/folder target, covers the current-folder surface, and refuses permission-denied, busy, missing, or connector targets with an explanation. ### Verification - `Core: npm run test:file-drop-zone (passed)` - `Files: npm run test:file-drop-target (passed)` - `Core WebUI production build (passed)` ### Next / Blocked - Keep open until the local commits are reviewed/integrated; then verify the server-side connector/write-policy response in the integrated UI and close if no gap remains. Suggested status label: `status/in-progress`
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-files#32
No description provided.