@ethora/chat-component 26.7.3 → 26.7.5

package/dist/components/MessageBubble/QuickReplies.d.ts

@@ -0,0 +1,18 @@
+import { default as React } from 'react';
+import { QuickReply } from '../../helpers/quickReplies';
+interface QuickRepliesProps {
+    replies: QuickReply[];
+    messageId: string;
+    accentColor?: string;
+    /** Already answered (in this session) - chips render disabled. */
+    answered?: boolean;
+    onSelect: (reply: QuickReply, questionId: string) => void;
+}
+/**
+ * Buttons offered by a bot message. Tapping one answers the message: the
+ * chips lock immediately (so a double tap cannot post two answers) and stay
+ * visible, which keeps the transcript readable - you can still see what the
+ * options were next to the answer that was picked.
+ */
+declare const QuickReplies: React.FC<QuickRepliesProps>;
+export default QuickReplies;

package/dist/helpers/quickReplies.d.ts

@@ -0,0 +1,31 @@
+/**
+ * One bot-offered button, as carried by the `quickReplies` attribute on a
+ * message stanza's <data> element. The wire format is the one the existing
+ * Ethora bots already emit (see ethora-backend/tools/web3-bots/*: they stamp
+ * `quickReplies: JSON.stringify(message.buttons)` with `{name, value}`
+ * objects), so nothing on the bot side has to change to light these up.
+ *
+ * `questionId` is the only addition: quiz-style flows need a stable id for
+ * the answer they collect, and it is optional so plain "yes/no" bots keep
+ * working. When it is absent we fall back to the button's index.
+ */
+export interface QuickReply {
+    /** Label shown on the chip. */
+    name: string;
+    /** Text sent back to the room when the chip is tapped. */
+    value: string;
+    /** Quiz question this button answers, used to build the answer URL. */
+    questionId?: string;
+}
+/**
+ * Decode the `quickReplies` payload into buttons. Deliberately forgiving:
+ * the attribute is written by bots (and, once the LLM-driven flow lands, by
+ * a model), so anything unparseable must degrade to "no buttons" rather
+ * than break the message. Accepts the already-decoded array too, since
+ * getDataFromXml decodes it in place the same way it does `mentions`.
+ */
+export declare const parseQuickReplies: (rawValue: unknown) => QuickReply[];
+export declare const markQuickRepliesAnswered: (messageId: string) => void;
+export declare const hasAnsweredQuickReplies: (messageId: string) => boolean;
+/** Test seam - the set is process-wide. */
+export declare const resetAnsweredQuickReplies: () => void;