{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/df5bf844af784dfe8986596d1cb39027\" 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/df5bf844af784dfe8986596d1cb39027-3db86c4a066dd4ae.gif","duration":152.468,"title":"Fixing Indentation and Code Block Boundaries","description":"This Loom focuses on fixing how code blocks are rendered in Obsidian by ensuring list continuation formatting works correctly. The speaker compares the evidence image behavior between Discord.dev.ref, the local database, and Obsidian, noting that unindented blocks fail to appear as continuations and create a spurious code block boundary that makes the [26] node illegible. They republish to address prior stale reload issues by using a force reload, then confirm the database now shows properly indented blocks after the update. The Loom ends after refreshing to verify the corrected rendering."}