feat(pipeline): render-derived shot thumbnails, and bulk shot delete
Deploy / deploy (push) Failing after 19m11s
Deploy / deploy (push) Failing after 19m11s
Two independent features landing together: Generated shot thumbnails — a shot can now carry a thumbnail promoted from a render export (Shot.generatedThumbnailUrl/generatedThumbnailFrom) alongside the existing brief-supplied thumbnailUrl, which always takes display precedence (lib/shot-thumbnail.ts) so a promoted frame can only ever fill a gap, never overwrite the brief. Shows with pipelineConfig.autoShotThumbnail promote automatically on every finished export (lib/render-pipeline/preview.ts); promoteExportThumbnail/ clearGeneratedThumbnail (actions/shots.ts) are the manual equivalent for everyone else. Worker-side seek logic for picking the promoted frame is covered by RenderWorker/VFXReviewWorker.Tests/ThumbnailSeekTests.cs. Bulk shot delete — the shot-status page's selection bar gets a "Bulk Actions" dropdown (alongside the existing Change Due Date) with Delete Shots. bulkDeleteShots() (actions/shots.ts) deletes one at a time rather than in a single statement: exports_shotId_fkey is ON DELETE RESTRICT by design, so a shot with renders or deliveries on record is protected and gets skipped and reported by name rather than aborting the whole selection or being silently destroyed along with its history. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,6 @@
|
||||
-- Thumbnail promoted from a render export. Kept separate from "thumbnailUrl"
|
||||
-- (the client-supplied reference frame) so promotion can only fill a gap and
|
||||
-- never overwrite the brief. Display precedence is
|
||||
-- COALESCE("thumbnailUrl", "generatedThumbnailUrl").
|
||||
ALTER TABLE "shots" ADD COLUMN "generatedThumbnailUrl" TEXT;
|
||||
ALTER TABLE "shots" ADD COLUMN "generatedThumbnailFrom" TEXT;
|
||||
@@ -411,6 +411,15 @@ model Shot {
|
||||
fps Float @default(24)
|
||||
dueDate DateTime?
|
||||
thumbnailUrl String?
|
||||
/// Thumbnail promoted from a render export — automatically when the project
|
||||
/// opts in via `pipelineConfig.autoShotThumbnail`, or by hand. Deliberately a
|
||||
/// separate column: `thumbnailUrl` is the client-supplied reference frame and
|
||||
/// is never written by the pipeline, so promotion can only fill a gap, never
|
||||
/// destroy the brief. Display precedence is `thumbnailUrl ?? generatedThumbnailUrl`
|
||||
/// (lib/shot-thumbnail.ts).
|
||||
generatedThumbnailUrl String?
|
||||
/// Version string of the export the generated thumbnail came from, e.g. "v004".
|
||||
generatedThumbnailFrom String?
|
||||
originalFootageUrl String?
|
||||
originalFootageKey String?
|
||||
shotGroupId String?
|
||||
|
||||
Reference in New Issue
Block a user