<?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/04c228b06bb34b97894e345b46cf0abe&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/04c228b06bb34b97894e345b46cf0abe-00001.gif</thumbnail_url><duration>101.13333333333331</duration><title>The Importance of Evaluation Errors in Widget Props 👀</title><description>Hey there! In this Loom, I want to talk about why I believe it&apos;s crucial to have evaluation errors as part of widget props. Let me give you an example: I have a chart widget, and I accidentally make a syntax error in the data by removing a comma. Now, I know that I&apos;ll see a validation error, but what I want to do is capture that error and display a placeholder error message instead of passing it to the props. This is helpful because the user knows what&apos;s really going on in the widget and can take corrective action. If we were to just pass default values, we wouldn&apos;t see the error in the actual data, and when the user reselects the property pane, they won&apos;t see where the validation error is. This can really hamper a widget&apos;s functionality. So, I hope this helps you understand why I think evaluation errors are so important in widget props!</description></oembed>