Leo Vasanko
410a8a7568
- Add cista/fileserver.py: REST blueprint at /files with PUT upload, DELETE, MKCOL, POST cp/mv (combined), GET/HEAD static serving - Remove WS control handler and all ControlBase/Cmd protocol types - Frontend: SelectionToolbar, FileExplorer, Gallery now POST to /files instead of opening a control WebSocket per operation - Remove controlUrl export from WS.ts - Add tests: REST API, static streaming, path/escaping security - Catch ValueError from filename.sanitize and return 400 Bad Request
Cista Vue Frontend
The frontend is a Single-Page App implemented with Vue 3. Development uses the Vite server together with the main Python backend, but in production the latter also serves the prebuilt frontend files.
Recommended IDE Setup
VSCode + Volar (and disable Vetur) + TypeScript Vue Plugin (Volar).
Type Support for .vue Imports in TS
TypeScript cannot handle type information for .vue imports by default, so we replace the tsc CLI with vue-tsc for type checking. In editors, we need TypeScript Vue Plugin (Volar) to make the TypeScript language service aware of .vue types.
If the standalone TypeScript plugin doesn't feel fast enough to you, Volar has also implemented a Take Over Mode that is more performant. You can enable it by the following steps:
- Disable the built-in TypeScript Extension
- Run
Extensions: Show Built-in Extensionsfrom VSCode's command palette - Find
TypeScript and JavaScript Language Features, right click and selectDisable (Workspace)
- Run
- Reload the VSCode window by running
Developer: Reload Windowfrom the command palette.
Hot-Reload for Development
Run the backend
uv sync --dev
uv run cista --dev -l :8000
And the Vite server (in another terminal)
cd frontend
bun install
bun run dev
Browse to Vite, which will proxy API requests to port 8000. Both servers live reload changes.
Type-Check, Compile and Minify for Production
This is also called by uv build during Python packaging:
bun run build