feat(task): spec 0004 — task images migrated to stdt_task_images sub-resource
Task images were stored as a JSON-ish field on stdt_tasks. Spec 0004 (see
docs/task-images-migration.md) splits them into a dedicated sub-resource
stdt_task_images so each image is its own row with mime_type / file_name /
etag / size_bytes, accessed via /api/tasks/<id>/images/.
Frontend changes:
- new useTaskImages composable owning image state per edit dialog, with
eager-load priming in load() so thumbnails render and are clickable in
the grid (fixes v-if branch gated on populated imageCache).
- taskService refactored: listTaskImages / createTaskImage / deleteTaskImage
/ getTaskImageContent (blob fetch with responseType: 'blob' to dodge 406s).
- apiEndpoints.TASKS.IMAGES added for documentation purposes only — services
still hardcode paths (CLAUDE.md flags apiEndpoints as stale).
- TaskView.vue: switched from inline task.images to useTaskImages(); image
upload / preview / delete / carousel wired to the new composable. Explicit
taskId passed to load() and commit() since useTaskImages is instantiated
without a taskIdRef at module scope.
- locales en/zh-CN: new image keys (addImage, pendingUpload, clickToLoad,
imagePartialFailure, imageLimitReached, etc.).
Tests:
- src/__tests__/api/taskService.test.js
- src/__tests__/composables/useTaskImages.test.js
- src/__tests__/composables/useTaskImages.network.test.js
Also: .claude/ added to .gitignore (Claude Code local permissions, per-dev).
Co-Authored-By:
Claude <noreply@anthropic.com>
Please register or sign in to comment