<?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/19031dd5121b48689ce6e028b9b4e295&quot; frameborder=&quot;0&quot; width=&quot;1550&quot; height=&quot;1162&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1162</height><width>1550</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1162</thumbnail_height><thumbnail_width>1550</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/19031dd5121b48689ce6e028b9b4e295-00001.gif</thumbnail_url><duration>173.99376186100002</duration><title>Issues with rendering nested components</title><description>In this video, I discuss the challenges I encountered while trying to understand how server-side rendering of nested components works. I highlight an issue and explore potential solutions before switching to server-side rendering. I demonstrate the problem by focusing on step 1 of a wizard, where the model in the Python file is not properly connected to the HTML file. I explain my expectations and show the discrepancy between the expected and actual results. Throughout the video, I analyze the code and breakpoints to identify the root cause of the issue.</description></oembed>