<?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/bde6da6766f0435aa4af39b57678706f&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/bde6da6766f0435aa4af39b57678706f-d6861ba15823690c.gif</thumbnail_url><duration>160.295</duration><title>Exploring the Second Entry Point and Observer Settings in Our Plugin 🚀</title><description>In this second part of the video, I discuss the entry point for initializing observers and listeners when loading the plugin. I highlight the PageTitleObserver and the importance of passing the findDiscourseNode and FeatureFlag for suggesting node input. We also check specific settings whenever the observer loads, which is efficient and takes only three to five milliseconds for each search call. I explain how we thread these settings through all observer calls to ensure smooth functionality. Please take a look at the changes made and understand why they were necessary.</description></oembed>