nandi/oripublic Fork 0
4166f8fba899b222fab287c398dcab9bf6f6e5c9
Commits
Clone
git clone https://git.rickub.com/nandi/ori.git
git clone ssh://git@rickub.com/nandi/ori.git

Host key fingerprint (ed25519): SHA256:iycHnxEyq0Q7uyVpB7JlznP0G7JrTPXLYRcAU5CSLhc — verify it before your first connect.

forked from bots-garden/ori

🛟 Updated. f5c963a · on 4166f8fba899b222fab287c398dcab9bf6f6e5c9 · k33g · 22h ago
0017-upload-files-with-drag-and-drop.yaml · 41 lines · 1.5 KBYAML Blame HistoryRaw
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
# Managed by IssueSpec. Hand edits are welcome; keep the schema valid.
id: 17
title: Upload files with drag and drop
state: open
author:
  name: k33g
  email: ph.charriere@gmail.com
createdAt: 2026-09-18T00:00:00.000Z
updatedAt: 2026-09-18T00:00:00.000Z
labels: []
body: |
  Add the ability to upload files to the workspace using drag and drop.

  Requirements:
  - Drag and drop files from the host OS into the browser
  - Upload files to the workspace directory (under `--cwd`)
  - Visual feedback during drag (drop zone highlight)
  - Progress indication for uploads
  - Support for multiple files
  - Support for directories (optional)

  Implementation considerations:
  - Backend: New endpoint for file uploads (e.g., `POST /api/upload` or extend `PUT /api/file`)
  - Frontend: Drag and drop handlers on the workspace panel or file tree
  - Should respect the existing 5 MiB file size limit (or adjust if needed)
  - Binary file handling (currently rejected with 415)
  - Destination path selection (drop on directory vs. root)
  - File tree refresh after upload

  Related existing functionality:
  - `PUT /api/file` already handles file writes (text only, <5 MiB)
  - File tree displays the workspace contents
  - Binary files currently rejected (415 Unsupported Media Type)

  Open questions:
  - Allow binary file uploads or keep text-only restriction?
  - Maximum total upload size (per request or cumulative)?
  - Overwrite confirmation for existing files?
  - Should drop target be the entire workspace panel, specific file tree area, or both?
tasks: []
comments: []