@trops/dash-core 0.1.552 → 0.1.554

package/dist/index.esm.js

@@ -12776,7 +12776,12 @@ var WidgetConfigPanel = function WidgetConfigPanel(_ref) {
     itemSelected = _useState2[0],
     setItemSelected = _useState2[1];
   useEffect(function () {
-    if (item !== itemSelected) {
+    // Only sync from the parent when the data actually differs.
+    // Identity-only comparison fired on every parent re-render
+    // (each edit round-trips through onChange → parent setState →
+    // new item reference) and reset the input mid-keystroke,
+    // making the userConfig inputs effectively untypeable.
+    if (JSON.stringify(item) !== JSON.stringify(itemSelected)) {
       setItemSelected(function () {
         return item;
       });
@@ -12842,7 +12847,15 @@ var WidgetConfigPanel = function WidgetConfigPanel(_ref) {
       newItem["userPrefs"] = {};
     }
     newItem["userPrefs"][key] = value;
-    //setItemSelected(() => newItem);
+    // Update local state immediately so the input reflects each
+    // keystroke without waiting for the parent round-trip to come
+    // back through props. Without this the InputText's `value` prop
+    // stays at the pre-keystroke value, the typed char visibly
+    // snaps away, and typing more than ~1 char per second is
+    // effectively impossible.
+    setItemSelected(function () {
+      return newItem;
+    });
     onChange(null, newItem);
   }
 
@@ -63042,6 +63055,56 @@ function ChatCore(_ref) {
     // eslint-disable-next-line react-hooks/exhaustive-deps
   }, [initialMessage, mainApi, messages, isCliBackend, cliAvailable, isLoading]);
 
+  // Slice 19H — external "send this message" hook.
+  //
+  // Some parent components (the widget builder modal's "Send error to AI"
+  // banner, the Console tab's per-error Send-to-AI button) need to push
+  // a user message into THIS chat conversation without rendering the
+  // input themselves. They dispatch a window CustomEvent named
+  // `dash:chat-core-send` with `detail: { persistKey, content, hidden? }`.
+  //
+  // Each ChatCore instance only reacts to events targeting its own
+  // persistKey OR sessionKey OR uuid — so the dashboard's AssistantPanel
+  // and the widget builder's chat don't cross-talk.
+  //
+  // Why a CustomEvent (not localStorage poll, not ref): the prior
+  // approach was for parent code to write to localStorage directly,
+  // hoping ChatCore would notice. ChatCore reads localStorage only at
+  // mount — so externally-written messages were silently dropped.
+  // CustomEvent is one-way + synchronous + zero-cost when nobody fires
+  // it, and stays consistent with the existing
+  // `dash:open-settings-create-provider` / `dash:provider-installed` /
+  // `dash:open-widget-builder` event bus used elsewhere in the app.
+  useEffect(function () {
+    var myKey = persistKey || sessionKey || uuid || null;
+    if (!myKey) return;
+    if (typeof window === "undefined") return;
+    var handler = function handler(event) {
+      var detail = event && event.detail;
+      if (!detail) return;
+      var targetKey = detail.persistKey || detail.sessionKey || detail.uuid || null;
+      if (targetKey !== myKey) return;
+      var content = detail.content;
+      if (typeof content !== "string" || content.length === 0) return;
+      // hidden defaults to false — the user typically WANTS to see the
+      // error-fix request in the chat history so it's clear what was
+      // sent and what the AI responded to.
+      var hidden = detail.hidden === true;
+      try {
+        handleSend(content, {
+          hidden: hidden
+        });
+      } catch (e) {
+        // Sending may fail (no API key, no CLI). Swallow — the parent
+        // can't recover beyond surfacing its own error state.
+      }
+    };
+    window.addEventListener("dash:chat-core-send", handler);
+    return function () {
+      return window.removeEventListener("dash:chat-core-send", handler);
+    };
+  }, [persistKey, sessionKey, uuid, handleSend]);
+
   // New chat
   var handleNewChat = function handleNewChat() {
     var _mainApi$llm3;