{"version":3,"file":"ChatActionsMenu.cjs","names":[],"sources":["../../../src/components/Chat/ChatActionsMenu.tsx"],"sourcesContent":["import type { ReactNode } from \"react\";\n\nimport { ContextMenu, type ContextMenuItem } from \"../ContextMenu\";\n\nexport interface ChatActionsMenuProps {\n    /** Actions for this message. */\n    items: ContextMenuItem[];\n    /** Which pointer gesture opens it — the bubble uses the right click, the ⋮ the left. */\n    trigger: \"contextmenu\" | \"click\";\n    /** The bubble, or the ⋮ button. */\n    children: ReactNode;\n}\n\n/**\n * The bridge from a message to the SDK's context menu.\n *\n * A separate module, reached through `lazy()` from the bubble, because\n * `ContextMenu` pulls `Portal` and its own geometry — measured, that is 3.07 kB\n * brotli — and a support thread or a comment list passes no `messageActions` at\n * all. Keeping it behind the dynamic import is what lets a text-only thread stay\n * the size it was.\n *\n * @param props - The items, the gesture and the trigger content.\n * @returns The content wrapped in a context menu.\n */\nexport function ChatActionsMenu({ items, trigger, children }: ChatActionsMenuProps) {\n    return (\n        <ContextMenu items={items} trigger={trigger}>\n            {children}\n        </ContextMenu>\n    );\n}\n"],"mappings":"qFAyBA,SAAgB,EAAgB,CAAE,QAAO,UAAS,YAAkC,CAChF,OACI,EAAA,EAAA,IAAA,CAAC,EAAA,YAAD,CAAoB,QAAgB,UAC/B,UACQ,CAAA,CAErB"}