@nocobase/plugin-ai 2.2.0-alpha.7 → 2.2.0-beta.10

package/dist/ai/docs/nocobase/workflow/development/node.md

@@ -1,9 +1,3 @@
----
-title: "Extending Node Types"
-description: "Extending node types: custom node development, node configuration, execution logic, API and lifecycle."
-keywords: "workflow,extending nodes,custom nodes,node development,NocoBase"
----
-
 # Extending Node Types
 
 A node's type is essentially an operational instruction. Different instructions represent different operations executed in the workflow.
@@ -117,7 +111,7 @@ export class AsyncInstruction extends Instruction {
     // 2. Explicitly call exit() to flush the task to the database and commit the transaction
     await processor.exit();
 
-    // 3. Initiate the async operation (transaction is now committed, no longer holding the DB connection)
+    // 3. Initiate the async operation (the transaction is now committed, no longer holding the database connection)
     const jobDone: IJob = { status: JOB_STATUS.PENDING };
     try {
       const result = await someAsyncOperation(node.config);
@@ -245,78 +239,44 @@ Similar to triggers, the configuration form for an instruction (node type) needs
 
 All instructions need to be derived from the `Instruction` base class. The related properties and methods are used for configuring and using the node.
 
-For example, if we need to provide a configuration interface for the random number string type (`randomString`) node defined on the server-side above, which has a configuration item `digit` representing the number of digits for the random number:
+For example, if we need to provide a configuration interface for the random number string type (`randomString`) node defined on the server-side above, which has a configuration item `digit` representing the number of digits for the random number, we would use a number input box in the configuration form to receive user input.
 
-```ts
-import { Instruction } from '@nocobase/plugin-workflow/client-v2';
+```tsx pure
+import WorkflowPlugin, { Instruction, VariableOption } from '@nocobase/workflow/client';
 
-class RandomStringInstruction extends Instruction {
+class MyInstruction extends Instruction {
   title = 'Random number string';
   type = 'randomString';
   group = 'extended';
-
-  // Node config form (lazy-loaded component)
-  FieldsetLoader = () => import('./components/RandomStringConfig');
-
-  useVariables(node, options) {
-    return { value: node.key, label: node.title };
+  fieldset = {
+    'digit': {
+      type: 'number',
+      title: 'Digit',
+      name: 'digit',
+      'x-decorator': 'FormItem',
+      'x-component': 'InputNumber',
+      'x-component-props': {
+        min: 1,
+        max: 10,
+      },
+      default: 6,
+    },
+  };
+  useVariables(node, options): VariableOption {
+    return {
+      value: node.key,
+      label: node.title,
+    };
   }
 }
-```
-
-Here, `FieldsetLoader` is a function that returns `Promise<{ default: ComponentType }>`, implementing lazy loading via dynamic `import()`. The component it points to is a standard React function component that builds the form using antd's `Form.Item`:
-
-```tsx
-// components/RandomStringConfig.tsx
-import { Form, InputNumber } from 'antd';
-
-export default function RandomStringConfig() {
-  return (
-    <Form.Item
-      name={['config', 'digit']}
-      label="Digit"
-      initialValue={6}
-      rules={[{ required: true }]}
-    >
-      <InputNumber min={1} max={10} />
-    </Form.Item>
-  );
-}
-```
-
-Note that the form field's `name` uses the nested array format `['config', 'fieldName']`, which is the standard antd Form convention.
-
-### Multiple Configuration Interfaces
-
-A node can provide multiple configuration interfaces for different scenarios:
-
-- `FieldsetLoader` — Node configuration drawer form (most commonly used)
-![FieldsetLoader](https://static-docs.nocobase.com/20260701153106.png)
-
-- `PresetFieldsetLoader` — Preset form when creating a node (usually contains only required fields)
-![PresetFieldsetLoader](https://static-docs.nocobase.com/20260701153041.png)
-
-- `ComponentLoader` — Custom node rendering on the canvas (used for branch nodes and other cases requiring special rendering)
-![ComponentLoader](https://static-docs.nocobase.com/20260701153139.png)
-
-When a Loader needs to point to a named export (rather than the default export) in a file, use `.then()` to remap:
-
-```ts
-FieldsetLoader = () => import('./components/MyNodeConfig').then((m) => ({ default: m.MyFieldset }));
-```
 
-### Register the Node
-
-Register the node type with the workflow plugin instance within the extended plugin:
-
-```ts
-import { Plugin } from '@nocobase/client-v2';
-import RandomStringInstruction from './RandomStringInstruction';
+export default class MyPlugin extends Plugin {
+  load() {
+    // get workflow plugin instance
+    const workflowPlugin = this.app.getPlugin<WorkflowPlugin>(WorkflowPlugin);
 
-export default class extends Plugin {
-  async load() {
-    const workflow = this.app.pm.get('workflow');
-    workflow.registerInstruction('randomString', RandomStringInstruction);
+    // register instruction
+    workflowPlugin.registerInstruction('randomString', MyInstruction);
   }
 }
 ```
@@ -327,7 +287,7 @@ The node type identifier registered on the client-side must be consistent with t
 
 ### Providing Node Results as Variables
 
-You may notice the `useVariables` method in the example above. If you need to use the node's result (the `result` part) as a variable for subsequent nodes, you need to implement this method in the derived instruction class and return an object that conforms to the `VariableOption` type. This object serves as a structural description of the node's execution result, providing variable name mapping for selection and use in subsequent nodes.
+You may notice the `useVariables` method in the example above. If you need to use the node's result (the `result` part) as a variable for subsequent nodes, you need to implement this method in the inherited instruction class and return an object that conforms to the `VariableOption` type. This object serves as a structural description of the node's execution result, providing variable name mapping for selection and use in subsequent nodes.
 
 The `VariableOption` type is defined as follows:
 
@@ -342,7 +302,7 @@ export type VariableOption = {
 
 The core is the `value` property, which represents the segmented path value of the variable name. `label` is used for display on the interface, and `children` is used to represent a multi-level variable structure, which is used when the node's result is a deeply nested object.
 
-A usable variable is represented internally in the system as a path template string separated by `.`, for example, `{{$jobsMapByNodeKey.2dw92cdf.abc}}`. Here, `$jobsMapByNodeKey` represents the result set of all nodes (internally defined, no need to handle), `2dw92cdf` is the node's `key`, and `abc` is a custom property in the node's result object.
+A usable variable is represented internally in the system as a path template string separated by `.`, for example, `{{jobsMapByNodeKey.2dw92cdf.abc}}`. Here, `jobsMapByNodeKey` represents the result set of all nodes (internally defined, no need to handle), `2dw92cdf` is the node's `key`, and `abc` is a custom property in the node's result object.
 
 Additionally, since a node's result can also be a simple value, when providing node variables, the first level **must** be the description of the node itself:
 
@@ -353,10 +313,14 @@ Additionally, since a node's result can also be a simple value, when providing n
 }
 ```
 
-That is, the first level is the node's `key` and title. For example, in the Calculation node's [code reference](https://github.com/nocobase/nocobase/blob/develop/packages/plugins/%40nocobase/plugin-workflow/src/client-v2/nodes/calculation.tsx), when using the result of the Calculation node, the interface options are as follows:
+That is, the first level is the node's `key` and title. For example, in the calculation node's [code reference](https://github.com/nocobase/nocobase/blob/main/packages/plugins/%40nocobase/plugin-workflow/src/client/nodes/calculation.tsx#L77), when using the result of the calculation node, the interface options are as follows:
+
+
 
 ![Result of Calculation Node](https://static-docs.nocobase.com/20240514230014.png)
 
+
+
 When the node's result is a complex object, you can use `children` to continue describing nested properties. For example, a custom instruction might return the following JSON data:
 
 ```json
@@ -364,7 +328,7 @@ When the node's result is a complex object, you can use `children` to continue d
   "message": "ok",
   "data": {
     "id": 1,
-    "name": "test"
+    "name": "test",
   }
 }
 ```
@@ -372,7 +336,7 @@ When the node's result is a complex object, you can use `children` to continue d
 Then you can return it through the `useVariables` method as follows:
 
 ```ts
-useVariables(node, options) {
+useVariables(node, options): VariableOption {
   return {
     value: node.key,
     label: node.title,
@@ -402,8 +366,12 @@ useVariables(node, options) {
 
 This way, in subsequent nodes, you can use the following interface to select variables from it:
 
+
+
 ![Mapped Result Variables](https://static-docs.nocobase.com/20240514230103.png)
 
+
+
 :::info{title="Note"}
 When a structure in the result is an array of deeply nested objects, you can also use `children` to describe the path, but it cannot include array indices. This is because in NocoBase workflow's variable handling, the variable path description for an array of objects is automatically flattened into an array of deep values when used, and you cannot access a specific value by its index.
 :::
@@ -413,6 +381,11 @@ When a structure in the result is an array of deeply nested objects, you can als
 By default, any node can be added to a workflow. However, in some cases, a node may not be applicable in certain types of workflows or branches. In such situations, you can configure the node's availability using `isAvailable`:
 
 ```ts
+// Type definition
+export abstract class Instruction {
+  isAvailable?(ctx: NodeAvailableContext): boolean;
+}
+
 export type NodeAvailableContext = {
   // Workflow plugin instance
   engine: WorkflowPlugin;
@@ -420,7 +393,7 @@ export type NodeAvailableContext = {
   workflow: object;
   // Upstream node
   upstream: object;
-  // Whether it is a branch node (branch index)
+  // Whether it is a branch node (branch number)
   branchIndex: number;
 };
 ```
@@ -430,17 +403,11 @@ The `isAvailable` method returns `true` if the node is available, and `false` if
 If there are no special requirements, you do not need to implement the `isAvailable` method, as nodes are available by default. The most common scenario requiring configuration is when a node might be a time-consuming operation and is not suitable for execution in a synchronous workflow. You can use the `isAvailable` method to restrict its use. For example:
 
 ```ts
-isAvailable({ engine, workflow }) {
+isAvailable({ engine, workflow, upstream, branchIndex }) {
   return !engine.isWorkflowSync(workflow);
 }
 ```
 
 ### Learn More
 
-For a complete real-world example, refer to: [CalculationInstruction source code](https://github.com/nocobase/nocobase/blob/develop/packages/plugins/%40nocobase/plugin-workflow/src/client-v2/nodes/calculation.tsx)
-
-For the definitions of various parameters for defining node types, see the [Workflow API Reference](./api) section.
-
-:::info{title=Note}
-If you were previously using the legacy (v1) client-side code and want to migrate to the new v2 version, refer to the [v1 to v2 Migration Guide](./migration).
-:::
+For the definitions of various parameters for defining node types, see the Workflow API Reference section.

package/dist/ai/docs/nocobase/workflow/development/trigger.md

@@ -1,10 +1,4 @@
----
-title: "Extending Trigger Types"
-description: "Extending trigger types: custom trigger development, configuration interface, trigger logic, API reference."
-keywords: "workflow,extending triggers,custom triggers,trigger development,NocoBase"
----
-
-# Extending Trigger Types
+# Extend Trigger Types
 
 Every workflow must be configured with a specific trigger, which serves as the entry point for starting the process execution.
 
@@ -68,129 +62,39 @@ After the server starts and loads, the `'interval'` type trigger can be added an
 
 The client-side part mainly provides a configuration interface based on the configuration items required by the trigger type. Each trigger type also needs to register its corresponding type configuration with the Workflow plugin.
 
-The trigger's configuration interface is defined through a Loader (lazy-loading function), which points to a plain React component that builds the form using antd's `Form.Item`.
-
-### The Simplest Trigger
-
-For example, for the interval timer trigger described above, define the interval time configuration item (`interval`) needed in the configuration interface form:
+For example, for the scheduled execution trigger mentioned above, define the required interval time configuration item (`interval`) in the configuration interface form:
 
 ```ts
-import { Trigger } from '@nocobase/plugin-workflow/client-v2';
+import { Trigger } from '@nocobase/workflow/client';
 
 class MyTrigger extends Trigger {
   title = 'Interval timer trigger';
-
-  // Trigger config form (lazy-loaded component)
-  FieldsetLoader = () => import('./IntervalConfig');
-
-  // Config validation
-  validate(config) {
-    return Boolean(config?.interval);
-  }
-}
-```
-
-Here, `FieldsetLoader` is a function that returns `Promise<{ default: ComponentType }>`, implementing lazy loading via dynamic `import()`. The component it points to is a standard React function component:
-
-```tsx
-// IntervalConfig.tsx
-import { Form, InputNumber } from 'antd';
-
-export default function IntervalConfig() {
-  return (
-    <Form.Item
-      name={['config', 'interval']}
-      label="Interval"
-      initialValue={60000}
-      rules={[{ required: true }]}
-    >
-      <InputNumber min={1000} />
-    </Form.Item>
-  );
+  // fields of trigger config
+  fieldset = {
+    interval: {
+      type: 'number',
+      title: 'Interval',
+      name: 'config.interval',
+      'x-decorator': 'FormItem',
+      'x-component': 'InputNumber',
+      default: 60000,
+    },
+  };
 }
 ```
 
-Note that the form field's `name` uses the nested array format `['config', 'fieldName']`, which is the standard antd Form convention.
-
-### Multiple Configuration Interfaces
-
-A trigger can provide multiple configuration interfaces for different scenarios:
-
-- `PresetFieldsetLoader` — Preset form when creating a workflow (usually contains only required fields)
-![PresetFieldsetLoader](https://static-docs.nocobase.com/20260701152711.png)
-
-- `FieldsetLoader` — Full trigger configuration form (displayed in the configuration drawer)
-![FieldsetLoader](https://static-docs.nocobase.com/20260701152822.png)
-
-- `TriggerFieldsetLoader` — Input form for manual execution
-![FieldsetLoader](https://static-docs.nocobase.com/20260701152846.png)
-
-When a Loader needs to point to a named export (rather than the default export) in a file, use `.then()` to remap:
+Then, register this trigger type with the workflow plugin instance within the extended plugin:
 
 ```ts
-class MyTrigger extends Trigger {
-  title = 'My trigger';
+import { Plugin } from '@nocobase/client';
+import WorkflowPlugin from '@nocobase/plugin-workflow/client';
 
-  PresetFieldsetLoader = () =>
-    import('./MyTriggerConfig').then((m) => ({ default: m.MyPresetConfig }));
-  FieldsetLoader = () => import('./MyTriggerConfig');
-  TriggerFieldsetLoader = () => import('./TriggerMyConfig');
-
-  validate(config) {
-    return Boolean(config?.collection && config?.mode);
-  }
-
-  createDefaultConfig() {
-    return { mode: 1 };
-  }
-}
-```
-
-```tsx
-// MyTriggerConfig.tsx
-import { Form, Select } from 'antd';
-import { CollectionCascader } from '@nocobase/plugin-workflow/client-v2';
-
-// Preset form for creation (named export)
-export function MyPresetConfig() {
-  return (
-    <Form.Item name={['config', 'collection']} label="Collection" rules={[{ required: true }]}>
-      <CollectionCascader />
-    </Form.Item>
-  );
-}
-
-// Full config form (default export)
-export default function MyTriggerConfig() {
-  return (
-    <>
-      <Form.Item name={['config', 'collection']} label="Collection">
-        <CollectionCascader disabled />
-      </Form.Item>
-      <Form.Item name={['config', 'mode']} label="Mode">
-        <Select
-          options={[
-            { label: 'Created', value: 1 },
-            { label: 'Updated', value: 2 },
-          ]}
-        />
-      </Form.Item>
-    </>
-  );
-}
-```
-
-### Register the Trigger
-
-Register the trigger type with the workflow plugin instance within the extended plugin:
-
-```ts
-import { Plugin } from '@nocobase/client-v2';
 import MyTrigger from './MyTrigger';
 
 export default class extends Plugin {
+  // You can get and modify the app instance here
   async load() {
-    const workflow = this.app.pm.get('workflow');
+    const workflow = this.app.pm.get(WorkflowPlugin) as WorkflowPlugin;
     workflow.registerTrigger('interval', MyTrigger);
   }
 }
@@ -202,10 +106,4 @@ After that, the new trigger type will be visible in the workflow configuration i
 The identifier of the trigger type registered on the client-side must be consistent with the one on the server-side, otherwise it will cause errors.
 :::
 
-For a complete real-world example, refer to: [CollectionTrigger source code](https://github.com/nocobase/nocobase/blob/develop/packages/plugins/%40nocobase/plugin-workflow/src/client-v2/triggers/collection/index.tsx)
-
-For other details on defining trigger types, please refer to the [Workflow API Reference](./api) section.
-
-:::info{title=Note}
-If you were previously using the legacy (v1) client-side code and want to migrate to the new v2 version, refer to the [v1 to v2 Migration Guide](./migration).
-:::
+For other details on defining trigger types, please refer to the [Workflow API Reference](./api#pluginregisterTrigger) section.

package/dist/ai/tools/subAgentWebSearch.js

@@ -40,12 +40,9 @@ var subAgentWebSearch_default = (0, import_ai.defineTools)({
   },
   definition: {
     name: "subAgentWebSearch",
-    description: "Search the web for current information. Put all independent search queries needed for this turn into one call so they can run in parallel. Do not call this tool repeatedly with similar queries unless the previous results are clearly insufficient for a critical missing fact.",
+    description: "Use the query to search the web and return concise, relevant findings with source links.",
     schema: import_zod.z.object({
-      query: import_zod.z.array(
-        import_zod.z.string(),
-        "A list of clear, specific, non-overlapping web search queries. Include all independent queries needed for this answer in a single tool call so they can run in parallel."
-      )
+      query: import_zod.z.array(import_zod.z.string(), "A clear and specific web search query describing the information to retrieve.")
     })
   },
   invoke: async (ctx, args, id) => {
@@ -54,8 +51,7 @@ var subAgentWebSearch_default = (0, import_ai.defineTools)({
     const { model } = ((_b = (_a = ctx.action) == null ? void 0 : _a.params) == null ? void 0 : _b.values) ?? {};
     const { provider } = await pluginAI.aiManager.getLLMService({
       ...model,
-      webSearch: true,
-      reasoning: { mode: "off" }
+      webSearch: true
     });
     if (!((_c = args.query) == null ? void 0 : _c.length)) {
       return {
@@ -89,20 +85,19 @@ var subAgentWebSearch_default = (0, import_ai.defineTools)({
     };
   }
 });
-const WEB_SEARCH_SYSTEM_PROMPT = `You are a web search retrieval assistant.
+const WEB_SEARCH_SYSTEM_PROMPT = `You are a web search assistant.
 
-Your output is for another AI model, not the final user-facing answer.
+Your primary task is to retrieve up-to-date information from the internet based on the user's input query.
 
 Requirements:
-1. Retrieve current, relevant information for the query.
-2. Return concise findings only. Do not write a polished final answer.
-3. Include source title, publisher/site, URL, and publication or update date when available.
-4. Prefer authoritative and recent sources.
-5. Distinguish confirmed facts from uncertain or incomplete information.
-6. Do not fabricate results, sources, dates, or URLs.
-7. If results are weak, say exactly what is missing instead of broadening the search yourself.
+1. Actively attempt web retrieval first. Use internet search to find relevant and recent information.
+2. Summarize and synthesize findings clearly and concisely.
+3. Explicitly cite sources for key points whenever possible (for example: website/publication name, article title, and URL if available).
+4. Distinguish confirmed facts from uncertain or incomplete information.
+5. Do not fabricate search results, sources, or real-time data.
+6. If you cannot access reliable real-time information from the internet, clearly and honestly state that real-time retrieval was not possible, then provide the best available general information with that limitation noted.
 
-Output format:
-- Findings: 3-6 concise bullet points.
-- Sources: numbered list with title, site, URL, and date when available.
-- Gaps: one short sentence if important information could not be verified.`;
+Output style:
+- Start with a brief direct answer.
+- Then provide a structured summary of findings.
+- End with a "Sources" section listing the origin of the information used.`;

package/dist/client/119.c6bf8c6433167d81.js

@@ -0,0 +1,10 @@
+/**
+ * This file is part of the NocoBase (R) project.
+ * Copyright (c) 2020-2024 NocoBase Co., Ltd.
+ * Authors: NocoBase Team.
+ *
+ * This project is dual-licensed under AGPL-3.0 and NocoBase Commercial License.
+ * For more information, please refer to: https://www.nocobase.com/agreement.
+ */
+
+"use strict";(self.webpackChunk_nocobase_plugin_ai=self.webpackChunk_nocobase_plugin_ai||[]).push([["119"],{4498:function(e,t,n){n.r(t),n.d(t,{CodeToolCard:function(){return y},buildToolCodeBlock:function(){return g},compactPatchForDisplay:function(){return f},shouldSkipCodeToolCardRender:function(){return p}});var r=n(9155),o=n.n(r),l=n(5475),a=n(4281);function i(e,t){(null==t||t>e.length)&&(t=e.length);for(var n=0,r=Array(t);n<t;n++)r[n]=e[n];return r}function c(e){return function(e){if(Array.isArray(e))return i(e)}(e)||function(e){if("u">typeof Symbol&&null!=e[Symbol.iterator]||null!=e["@@iterator"])return Array.from(e)}(e)||function(e){if(e){if("string"==typeof e)return i(e,void 0);var t=Object.prototype.toString.call(e).slice(8,-1);if("Object"===t&&e.constructor&&(t=e.constructor.name),"Map"===t||"Set"===t)return Array.from(t);if("Arguments"===t||/^(?:Ui|I)nt(?:8|16|32)(?:Clamped)?Array$/.test(t))return i(e,void 0)}}(e)||function(){throw TypeError("Invalid attempt to spread non-iterable instance.\\nIn order to be iterable, non-array objects must have a [Symbol.iterator]() method.")}()}function u(e,t){return"writeJSCode"===e?"string"==typeof t.code?t.code:void 0:"patchJSCode"===e&&"string"==typeof t.patch?t.patch:void 0}function s(e){var t=function(e){if("string"!=typeof e)return e;var t=e.trim();if(!t)return{};try{return JSON.parse((0,l.m)(t))}catch(e){return}}(e.args);return t&&(void 0===t?"undefined":t&&"u">typeof Symbol&&t.constructor===Symbol?"symbol":typeof t)=="object"?t:null}function p(e,t){if(!g(e.toolCall))return!1;var n,r=s(t.toolCall);if(!r)return!0;var o=u(e.toolCall.name,null!=(n=s(e.toolCall))?n:{}),l=u(t.toolCall.name,r);return!!o&&(!l||l.length<.8*o.length)}function f(e){for(var t,n=e&&null!=(t=e.match(/[^\n]*\n|[^\n]+/g))?t:[],r=[],o=0;o<n.length;){var l=n[o];if(!l.startsWith("@@ ")){r.push(l),o++;continue}r.push(l),o++;for(var a=[];o<n.length&&!n[o].startsWith("@@ ");)a.push(n[o]),o++;r.push.apply(r,c(function(e){var t=arguments.length>1&&void 0!==arguments[1]?arguments[1]:3,n=e.reduce(function(e,t,n){return(t.startsWith("+")||t.startsWith("-"))&&e.push(n),e},[]);if(!n.length||e.length<=80)return e;var r=new Set,o=!0,l=!1,a=void 0;try{for(var i,u=n[Symbol.iterator]();!(o=(i=u.next()).done);o=!0)for(var s=i.value,p=Math.max(0,s-t);p<=Math.min(e.length-1,s+t);p++)r.add(p)}catch(e){l=!0,a=e}finally{try{o||null==u.return||u.return()}finally{if(l)throw a}}var f=[],g=-1,y=!0,d=!1,m=void 0;try{for(var b,h=c(r).sort(function(e,t){return e-t})[Symbol.iterator]();!(y=(b=h.next()).done);y=!0){var v=b.value;-1!==g&&v>g+1&&f.push(" ...\n"),f.push(e[v]),g=v}}catch(e){d=!0,m=e}finally{try{y||null==h.return||h.return()}finally{if(d)throw m}}return f}(function(e){for(var t=[],n=0;n<e.length;){var r=e[n],o=e[n+1];if((null==r?void 0:r.startsWith("-"))&&(null==o?void 0:o.startsWith("+"))&&!r.startsWith("---")&&!o.startsWith("+++")&&r.slice(1)===o.slice(1)){t.push(" ".concat(r.slice(1))),n+=2;continue}t.push(r),n++}return t}(a))))}return r.join("")}function g(e){var t=s(e);return t?"writeJSCode"===e.name&&"string"==typeof t.code&&t.code?{language:"js",value:t.code}:"patchJSCode"===e.name&&"string"==typeof t.patch&&t.patch?{language:"diff",value:f(t.patch)}:null:null}var y=o().memo(function(e){var t=g(e.toolCall);return t?o().createElement("div",{style:{padding:"4px 12px"}},o().createElement(a.w,{className:"language-".concat(t.language)},t.value)):null},p)},4281:function(e,t,n){n.d(t,{w:function(){return S},Rs:function(){return C},Cy:function(){return P}});var r=n(9155),o=n.n(r),l=n(2059),a=n(7375),i=n(3342),c=n(3079),u=n(8680),s=n(7694),p=n(7546),f=n(7596);function g(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{},r=Object.keys(n);"function"==typeof Object.getOwnPropertySymbols&&(r=r.concat(Object.getOwnPropertySymbols(n).filter(function(e){return Object.getOwnPropertyDescriptor(n,e).enumerable}))),r.forEach(function(t){var r;r=n[t],t in e?Object.defineProperty(e,t,{value:r,enumerable:!0,configurable:!0,writable:!0}):e[t]=r})}return e}function y(e,t){return t=null!=t?t:{},Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(t)):(function(e){var t=Object.keys(e);if(Object.getOwnPropertySymbols){var n=Object.getOwnPropertySymbols(e);t.push.apply(t,n)}return t})(Object(t)).forEach(function(n){Object.defineProperty(e,n,Object.getOwnPropertyDescriptor(t,n))}),e}function d(e,t){if(null==e)return{};var n,r,o,l={};if("u">typeof Reflect&&Reflect.ownKeys){for(o=0,n=Reflect.ownKeys(Object(e));o<n.length;o++)r=n[o],!(t.indexOf(r)>=0)&&Object.prototype.propertyIsEnumerable.call(e,r)&&(l[r]=e[r]);return l}if(l=function(e,t){if(null==e)return{};var n,r,o={},l=Object.getOwnPropertyNames(e);for(r=0;r<l.length;r++)n=l[r],!(t.indexOf(n)>=0)&&Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n]);return o}(e,t),Object.getOwnPropertySymbols)for(o=0,n=Object.getOwnPropertySymbols(e);o<n.length;o++)r=n[o],!(t.indexOf(r)>=0)&&Object.prototype.propertyIsEnumerable.call(e,r)&&(l[r]=e[r]);return l}var m=(0,i.lazy)(function(){return Promise.all([n.e("428"),n.e("758")]).then(n.bind(n,2733))},"CodeHighlight").CodeHighlight,b=function(e){var t=e.language,n=e.value,r=e.height,l=e.scrollToBottom,a=d(e,["language","value","height","scrollToBottom"]);return o().createElement(m,y(g({},a),{language:t,value:n,height:r,scrollToBottom:l}))},h=function(e){var t=(0,s.useFlowContext)(),n=(0,c.kj)(),r=f.J.use.currentConversation(),i=(0,p.Y)(r),u=e.children,m=e.className,h=(e.node,e.message),O=d(e,["children","className","node","message"]),w=/language-(\w+)/.exec(m||""),E=w?w[1]:"",j=String(u).replace(/<!--[\s\S]*?-->/g,"").replace(/\n$/,""),C=l.App.useApp().message,S=!0;(null==h?void 0:h.type)==="text"&&(S=RegExp("```"+E+"[\\s\\S]*?```","s").test(h.content));var P=i.use.editorRef()[i.use.currentEditorRefUid()];return w?o().createElement(l.Card,{type:"inner",size:"small",title:o().createElement(l.Space,{style:{margin:"0 8px"},size:"middle"},o().createElement(a.CodeOutlined,null),o().createElement("span",null,E)),extra:o().createElement(o().Fragment,null,o().createElement(l.Tooltip,{title:n("Copy")},o().createElement(l.Button,{type:"text",icon:o().createElement(a.CopyOutlined,null),onClick:function(){navigator.clipboard.writeText(j),C.success(n("Copied"))}})),o().createElement(l.Divider,{type:"vertical"}),o().createElement(l.Tooltip,{title:n("Expand")},o().createElement(l.Button,{type:"text",icon:o().createElement(a.ExpandOutlined,null),onClick:function(){t.viewer.dialog({width:"80%",zIndex:6e3,content:o().createElement(v,y(g({},O),{language:E,value:j,height:"75vh"}))})}}))),styles:{header:{padding:0},body:{padding:0}},actions:P?[o().createElement(l.Button,{key:"accept",type:"link",onClick:function(e){e.stopPropagation(),null==P||P.write(j),t.message.info(n("Applied"))},disabled:!S},n("Apply to editor"))]:[]},o().createElement(b,y(g({},O),{language:E,value:j,scrollToBottom:!S}))):o().createElement(l.Typography.Text,y(g({code:!0},O),{className:m}),u)},v=function(e){var t=e.language,n=e.value,r=d(e,["language","value"]),i=(0,s.useFlowViewContext)(),c=i.view.Header,u=o().createElement(l.Button,{type:"text",icon:o().createElement(a.CloseOutlined,null),onClick:function(){i.view.close()}});return o().createElement("div",{style:{borderRadius:8}},o().createElement(c,{title:o().createElement(o().Fragment,null,o().createElement(l.Space,null,u,o().createElement("span",null,t)))}),o().createElement(b,y(g({},r),{language:t,value:n})))};function O(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{},r=Object.keys(n);"function"==typeof Object.getOwnPropertySymbols&&(r=r.concat(Object.getOwnPropertySymbols(n).filter(function(e){return Object.getOwnPropertyDescriptor(n,e).enumerable}))),r.forEach(function(t){var r;r=n[t],t in e?Object.defineProperty(e,t,{value:r,enumerable:!0,configurable:!0,writable:!0}):e[t]=r})}return e}function w(e,t){return t=null!=t?t:{},Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(t)):(function(e){var t=Object.keys(e);if(Object.getOwnPropertySymbols){var n=Object.getOwnPropertySymbols(e);t.push.apply(t,n)}return t})(Object(t)).forEach(function(n){Object.defineProperty(e,n,Object.getOwnPropertyDescriptor(t,n))}),e}function E(e,t){if(null==e)return{};var n,r,o,l={};if("u">typeof Reflect&&Reflect.ownKeys){for(o=0,n=Reflect.ownKeys(Object(e));o<n.length;o++)r=n[o],!(t.indexOf(r)>=0)&&Object.prototype.propertyIsEnumerable.call(e,r)&&(l[r]=e[r]);return l}if(l=function(e,t){if(null==e)return{};var n,r,o={},l=Object.getOwnPropertyNames(e);for(r=0;r<l.length;r++)n=l[r],!(t.indexOf(n)>=0)&&Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n]);return o}(e,t),Object.getOwnPropertySymbols)for(o=0,n=Object.getOwnPropertySymbols(e);o<n.length;o++)r=n[o],!(t.indexOf(r)>=0)&&Object.prototype.propertyIsEnumerable.call(e,r)&&(l[r]=e[r]);return l}var j=(0,i.lazy)(function(){return Promise.all([n.e("428"),n.e("758")]).then(n.bind(n,2733))},"CodeHighlight").CodeHighlight,C=function(e){var t=e.language,n=e.value,r=E(e,["language","value"]);return o().createElement(j,w(O({},r),{language:t,value:n}))},S=function(e){var t=e.children,n=e.className,r=(e.node,e.message,E(e,["children","className","node","message"])),u=/language-(\w+)/.exec(n||""),s=u?u[1]:"",p=(0,i.useToken)().token,f=(0,c.kj)(),g=String(t).replace(/\n$/,""),y=l.App.useApp().message;return u?o().createElement(l.Card,{size:"small",title:s,styles:{title:{fontSize:p.fontSize,fontWeight:400},body:{width:"100%",fontSize:p.fontSizeSM}},extra:o().createElement(l.Button,{variant:"link",color:"default",size:"small",onClick:function(){navigator.clipboard.writeText(g),y.success(f("Copied"))},icon:o().createElement(a.CopyOutlined,null)})},o().createElement(C,w(O({},r),{language:s,value:g}))):o().createElement(l.Typography.Text,w(O({code:!0},r),{className:n}),t)},P=function(e){var t=e.className,n=/language-(\w+)/.exec(t||""),r=n?n[1]:"",l=f.J.use.currentConversation(),a=(0,p.Y)(l);return a.use.editorRef()[a.use.currentEditorRefUid()]&&(0,u._t)(r)?o().createElement(h,e):o().createElement(S,e)}}}]);