US-1: Asset Import Pipeline — glTF upload endpoint with metadata extraction #27
Reference in New Issue
Block a user
Delete Branch "agent/25d5046bb30c"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Auto-opened by architect for task
25d5046bb30c.Dashboard: http://cloudbison:7070/task/25d5046bb30c
User Story: As a creator, I can import glTF models and textures into my experience so that I can use custom 3D assets.
Task: Extend the existing asset upload endpoint (
POST /api/assets/{id}/upload) to detect glTF/GLB files and extract metadata (mesh_count, vertex_count, has_animation, texture_refs, bounding_box). Add glTF-specific fields to the Asset model and response schema.Files:
backend/app/models/asset.py— add glTF metadata fields (mesh_count: int, vertex_count: int, has_animation: bool, texture_refs: list[str], bounding_box_min: list[float], bounding_box_max: list[float])backend/app/routers/assets.py— add glTF detection in upload endpoint, metadata extraction using a lightweight glTF parser (e.g.,gltfortrimesh), store metadata inmetadata_jsoncolumnbackend/app/config.py— addGLTF_MAX_FILE_SIZE_MBsetting if neededAcceptance Criteria:
/api/assets/{id}/uploadwith a.glb/.gltffile extracts mesh_count, vertex_count, has_animation, texture_refs, and bounding boxmetadata_jsonand returned in GET responseDependencies: None (builds on existing asset infrastructure)