{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/be97dc663e7c43678eb0f8debc8af35c\" frameborder=\"0\" width=\"1662\" height=\"1246\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1246,"width":1662,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1246,"thumbnail_width":1662,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/be97dc663e7c43678eb0f8debc8af35c-e39f56541ed58c05.gif","duration":102.761,"title":"Defining CrossAppAssetType and AssetLimits","description":"This Loom discusses PR 1864, which defines CrossAppAssetType and related database and contract changes. It introduces new fields including SourceRef, SourcePath (stored as FilePath), and a ContentHash, and updates CrossAppNode to include Assets along with an updated CrossAppNodeContract example. The author also covers the addition of AssetLimits, citing current Supabase limits and noting that oversized handling may be worth its own PR but is not separated out here. Finally, it mentions a shift from using the limits only as a constant in Obsidian to using the new limits, with accompanying tests and comments."}