@remotion/studio: Fix calculateMetadata copy on render errors#6996
@remotion/studio: Fix calculateMetadata copy on render errors#6996JonnyBurger merged 1 commit intomainfrom
@remotion/studio: Fix calculateMetadata copy on render errors#6996Conversation
Made-with: Cursor
|
Reviewed PR #6996 — no actionable issues found. The fix correctly differentiates render errors from Task list (3/3 completed)
|
@remotion/studio: Fix calculateMetadata copy on render errors
There was a problem hiding this comment.
Clean, focused fix. The two error paths in CanvasOrLoading are now correctly distinguished — render errors get a generic "Retry" button while resolution errors from calculateMetadata() get the specific label and explainer. Verified that the only other ErrorLoader call site (Overlay.tsx) already passes calculateMetadata={false}, so no additional changes are needed there.
Big Pickle (free) | 𝕏

Summary
CanvasOrLoadingalways passedcalculateMetadatatoErrorLoaderfor both (a) render errors fromRenderErrorContextand (b) composition resolution failures (resolved.type === 'error'). Only (b) is fromcalculateMetadata().RetryButtonalways saidRetry calculateMetadata()even when the error was not from metadata calculation (e.g. render errors).Changes
calculateMetadataContext={false}for render errors andtrueonly when showing resolution errors fromcalculateMetadata.RetryButtonaccepts an optionallabel(defaultRetry).ErrorDisplaysetsRetry calculateMetadata()only whencalculateMetadatais true.Related
@remotion/studio: Scroll to composition or asset when selected but out of view #6997 (sidebar scroll + asset metadata errors in canvas).