<?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/c374a122500e4148ba0bbfaf634aeb77&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/c374a122500e4148ba0bbfaf634aeb77-3b5239a659bc501e.gif</thumbnail_url><duration>238.864</duration><title>Improving Validation Logic in Tag and Format Components</title><description>In this video, I addressed the feedback regarding the complexity of the PR, specifically about the validation logic between the tag component and the format. I modified the code to clarify that the tag and format should not be the same, which is crucial for proper error handling. I demonstrated the changes made to the validated input panel and how we now communicate state changes more effectively. I hope the audio is clear, and I would appreciate any feedback on the build errors if they arise. Please let me know if you have any questions or need further clarification.</description></oembed>