<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/cb4e428ed0d647208a78a70fc31b734b&quot; frameborder=&quot;0&quot; width=&quot;1662&quot; height=&quot;1246&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1246</height><width>1662</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1246</thumbnail_height><thumbnail_width>1662</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/cb4e428ed0d647208a78a70fc31b734b-dce09eaf57b2eaa9.gif</thumbnail_url><duration>308.063</duration><title>Local Concept Input and Nested Content Changes</title><description>This Loom explains a PR that expands the concept local input type to support inline documents, authors, and creators when generating content. It adds fields like creatorLocalId, documentLocalId, contentLocalInput, and other parameters used to populate content, and also notes a minor change to fetch platform account data via a newly introduced accountLocalInline case. The author adjusts the content generation logic to populate upstream variables, call the existing absurd content function, and make failures propagate to the whole concept. It also covers downstream updates, including converting an absurd concept file to TypeScript, adding tests for inline behavior and nested page variants, and making Roam-specific documentation type changes to avoid TypeScript errors.</description></oembed>