<?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/d5a6d5b3c60e45ffa8cd3afe5fa14488&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/d5a6d5b3c60e45ffa8cd3afe5fa14488-83afe78ea0a9cbef.gif</thumbnail_url><duration>35.927</duration><title>Refactor FullContentToCrossApp Utility</title><description>This Loom discusses refactoring by extracting shared conversion logic into a new utility function named FullContentToCrossApp. The speaker isolates the code currently in ConvertRomeToFullContent and moves it into this utility to reuse in the current case. They note that FullContent might not be a widely reused type yet, but it is used in this implementation. Overall, the change focuses on making the conversion code easier to reuse and maintain.</description></oembed>