@knocklabs/agent-toolkit 0.1.2 → 0.1.3

package/dist/lib/tools/workflows.js

@@ -1,205 +1,8 @@
-// src/lib/tools/workflows.ts
-import { z as z2 } from "zod";
-
-// src/lib/knock-tool.ts
-import { z } from "zod";
-var trimLines = (text) => text.split("\n").map((l) => l.trim()).filter(Boolean).join("\n");
-var KnockTool = (args) => {
-  const { execute, ...restOfArgs } = args;
-  const parameters = restOfArgs.parameters ? restOfArgs.parameters : z.object({});
-  const schemaEntries = Object.entries(parameters.shape);
-  const argsStr = schemaEntries.length === 0 ? "Takes no arguments" : schemaEntries.map(([key, value]) => {
-    return `- ${key}: ${value.description || ""}`;
-  }).join("\n");
-  const fullDescription = trimLines(`
-  Tool name:
-  ${args.name}
-  Description:
-  ${args.description}.
-  Arguments:
-  ${argsStr}
-  `);
-  return {
-    ...restOfArgs,
-    parameters,
-    fullDescription,
-    bindExecute: (knockClient, config) => execute(knockClient, config)
-  };
-};
-
-// src/lib/tools/workflows.ts
-var listWorkflows = KnockTool({
-  method: "list_workflows",
-  name: "List workflows",
-  description: `
-  List all workflows available for the given environment. Returns structural information about the workflows, including the key, name, description, and categories. Will also return the steps that make up the workflow. 
-
-  Use this tool when you need to understand which workflows are available to be called. 
-  `,
-  parameters: z2.object({
-    environment: z2.string().describe(
-      "(string): The environment to list workflows for. Defaults to `development`."
-    )
-  }),
-  execute: (knockClient, config) => async (params) => {
-    const allWorkflows = [];
-    const listParams = {
-      environment: params.environment ?? config.environment ?? "development"
-    };
-    for await (const workflow of knockClient.workflows.list(listParams)) {
-      allWorkflows.push(workflow);
-    }
-    return allWorkflows;
-  }
-});
-var triggerWorkflow = KnockTool({
-  method: "trigger_workflow",
-  name: "Trigger workflow",
-  description: `
-  Trigger a workflow for one or more recipients.
-
-  Use this tool when you need to trigger a workflow to send a notification across the channels configured for the workflow. The workflow must be committed in the environment for you to trigger it.
-
-  When recipients aren't provided, the workflow will be triggered for the current user specified in the config.
-  `,
-  parameters: z2.object({
-    workflowKey: z2.string().describe("(string): The key of the workflow to trigger."),
-    recipients: z2.array(z2.string()).describe("(array): The recipients to trigger the workflow for."),
-    data: z2.record(z2.string(), z2.any()).describe("(object): Data to pass to the workflow."),
-    tenant: z2.record(z2.string(), z2.any()).describe(
-      "(object): The tenant to trigger the workflow for. Must contain an id if being sent."
-    )
-  }),
-  execute: (knockClient, config) => async (params) => {
-    const publicClient = await knockClient.publicApi();
-    const result = await publicClient.workflows.trigger(params.workflowKey, {
-      recipients: params.recipients,
-      data: params.data,
-      tenant: params.tenant
-    });
-    return result.workflow_run_id;
-  }
-});
-var createEmailWorkflow = KnockTool({
-  method: "create_email_workflow",
-  name: "Create email workflow",
-  description: `
-  Creates a simple email workflow with a single step that sends an email to the recipient. Use this tool when you need to need to create an email notification, and you don't need to specify any additional steps. You can only create workflows in the development environment.
-
-  The content of the email you supply should ONLY ever be in markdown format for simplicity. You can supply dynamic variables to the subject and body of the email using the liquid template language.
-
-  When writing markdown, be sure to use headings (##) to separate sections of the email. Use an informal writing style, and avoid using complex language.
-
-  The following variables are available to use in the email subject and body:
-
-  - \`recipient.name\`: The name of the recipient.
-  - \`recipient.email\`: The email of the recipient.
-  - \`recipient.phone_number\`: The phone number of the recipient.
-  - \`tenant.id\`: The id of the tenant.
-  - \`tenant.name\`: The name of the tenant.
-
-  You can supply any other dynamic variables by referencing them under the \`data\` key in the \`data\` parameter when triggering the workflow. You add those like \`{{ data.variable_name }}\`.
-
-  You can also supply a list of categories to the workflow. These are used to categorize workflows for notification preferences. Categories should be supplied as lowercase strings in kebab case.
-
-  Once you've created the workflow, you should ask if you should commit the changes to the environment.
-  `,
-  parameters: z2.object({
-    environment: z2.string().describe(
-      "(string): The environment to create the workflow in. Defaults to `development`."
-    ),
-    workflowKey: z2.string().describe("(string): The key of the workflow."),
-    name: z2.string().describe("(string): The name of the workflow."),
-    categories: z2.array(z2.string()).describe("(array): The categories to add to the workflow."),
-    subject: z2.string().describe("(string): The subject of the email."),
-    body: z2.string().describe("(string): The body of the email.")
-  }),
-  execute: (knockClient, config) => async (params) => {
-    const emailChannelsPage = await knockClient.channels.list();
-    const emailChannels = emailChannelsPage.entries.filter(
-      (channel) => channel.type === "email"
-    );
-    if (emailChannels.length === 0) {
-      throw new Error("No email channels found");
-    }
-    const workflowParams = {
-      environment: params.environment ?? config.environment ?? "development",
-      workflow: {
-        name: params.name,
-        categories: params.categories ?? [],
-        steps: [
-          {
-            type: "channel",
-            channel_key: emailChannels[0].key,
-            template: {
-              settings: {
-                layout_key: "default"
-              },
-              subject: params.subject,
-              visual_blocks: [
-                // @ts-ignore
-                {
-                  type: "markdown",
-                  content: params.body
-                }
-              ]
-            },
-            name: "Email",
-            ref: "email_1"
-          }
-        ]
-      }
-    };
-    return await knockClient.workflows.upsert(
-      params.workflowKey,
-      workflowParams
-    );
-  }
-});
-var createOneOffWorkflowSchedule = KnockTool({
-  method: "create_one_off_workflow_schedule",
-  name: "Create one-off workflow schedule",
-  description: `
-  Create a one-off workflow schedule for a user. Use this tool when you need to schedule the execution of a workflow for a specific user in the future, like to power a delayed notification.
-  
-  Schedules can accept a set of data that will be passed to the workflow trigger when it is executed. When the userId is not provided, the schedule will be created for the current user specified in the config.
-
-  Examples:
-  
-  - In three days, send a welcome email to a user
-  - In one hour, send a password reset email to a user
-  - In two weeks, send a survey to a user
-  `,
-  parameters: z2.object({
-    workflowKey: z2.string().describe("(string): The key of the workflow to schedule."),
-    userId: z2.string().describe(
-      "(string): The userId of the user to schedule the workflow for."
-    ),
-    scheduledAt: z2.string().describe(
-      "(string): The date and time to schedule the workflow for. Must be in ISO 8601 format."
-    ),
-    data: z2.record(z2.string(), z2.any()).describe("(object): Data to pass to the workflow.")
-  }),
-  execute: (knockClient, config) => async (params) => {
-    const publicClient = await knockClient.publicApi();
-    return await publicClient.workflows.createSchedules(params.workflowKey, {
-      recipients: [params.userId ?? config.userId],
-      scheduled_at: params.scheduledAt,
-      data: params.data
-    });
-  }
-});
-var workflows = {
-  listWorkflows,
-  triggerWorkflow,
-  createEmailWorkflow,
-  createOneOffWorkflowSchedule
-};
-var permissions = {
-  read: ["listWorkflows"],
-  manage: ["createEmailWorkflow", "createOneOffWorkflowSchedule"],
-  trigger: ["triggerWorkflow"]
-};
+import {
+  permissions,
+  workflows
+} from "../../chunk-XRQWR3LY.js";
+import "../../chunk-TOBLV65T.js";
 export {
   permissions,
   workflows

package/dist/lib/tools/workflows.js.map

@@ -1 +1 @@
-{"version":3,"sources":["../../../src/lib/tools/workflows.ts","../../../src/lib/knock-tool.ts"],"sourcesContent":["import { z } from \"zod\";\nimport { KnockTool } from \"../knock-tool.js\";\nimport {\n  Workflow,\n  WorkflowUpsertParams,\n} from \"@knocklabs/mgmt/resources/index.js\";\n\nconst listWorkflows = KnockTool({\n  method: \"list_workflows\",\n  name: \"List workflows\",\n  description: `\n  List all workflows available for the given environment. Returns structural information about the workflows, including the key, name, description, and categories. Will also return the steps that make up the workflow. \n\n  Use this tool when you need to understand which workflows are available to be called. \n  `,\n  parameters: z.object({\n    environment: z\n      .string()\n      .describe(\n        \"(string): The environment to list workflows for. Defaults to `development`.\"\n      ),\n  }),\n  execute: (knockClient, config) => async (params) => {\n    const allWorkflows: Workflow[] = [];\n    const listParams = {\n      environment: params.environment ?? config.environment ?? \"development\",\n    };\n\n    for await (const workflow of knockClient.workflows.list(listParams)) {\n      allWorkflows.push(workflow);\n    }\n    return allWorkflows;\n  },\n});\n\nconst triggerWorkflow = KnockTool({\n  method: \"trigger_workflow\",\n  name: \"Trigger workflow\",\n  description: `\n  Trigger a workflow for one or more recipients.\n\n  Use this tool when you need to trigger a workflow to send a notification across the channels configured for the workflow. The workflow must be committed in the environment for you to trigger it.\n\n  When recipients aren't provided, the workflow will be triggered for the current user specified in the config.\n  `,\n  parameters: z.object({\n    workflowKey: z\n      .string()\n      .describe(\"(string): The key of the workflow to trigger.\"),\n    recipients: z\n      .array(z.string())\n      .describe(\"(array): The recipients to trigger the workflow for.\"),\n    data: z\n      .record(z.string(), z.any())\n      .describe(\"(object): Data to pass to the workflow.\"),\n    tenant: z\n      .record(z.string(), z.any())\n      .describe(\n        \"(object): The tenant to trigger the workflow for. Must contain an id if being sent.\"\n      ),\n  }),\n  execute: (knockClient, config) => async (params) => {\n    const publicClient = await knockClient.publicApi();\n\n    const result = await publicClient.workflows.trigger(params.workflowKey, {\n      recipients: params.recipients,\n      data: params.data,\n      tenant: params.tenant,\n    });\n\n    return result.workflow_run_id;\n  },\n});\n\nconst createEmailWorkflow = KnockTool({\n  method: \"create_email_workflow\",\n  name: \"Create email workflow\",\n  description: `\n  Creates a simple email workflow with a single step that sends an email to the recipient. Use this tool when you need to need to create an email notification, and you don't need to specify any additional steps. You can only create workflows in the development environment.\n\n  The content of the email you supply should ONLY ever be in markdown format for simplicity. You can supply dynamic variables to the subject and body of the email using the liquid template language.\n\n  When writing markdown, be sure to use headings (##) to separate sections of the email. Use an informal writing style, and avoid using complex language.\n\n  The following variables are available to use in the email subject and body:\n\n  - \\`recipient.name\\`: The name of the recipient.\n  - \\`recipient.email\\`: The email of the recipient.\n  - \\`recipient.phone_number\\`: The phone number of the recipient.\n  - \\`tenant.id\\`: The id of the tenant.\n  - \\`tenant.name\\`: The name of the tenant.\n\n  You can supply any other dynamic variables by referencing them under the \\`data\\` key in the \\`data\\` parameter when triggering the workflow. You add those like \\`{{ data.variable_name }}\\`.\n\n  You can also supply a list of categories to the workflow. These are used to categorize workflows for notification preferences. Categories should be supplied as lowercase strings in kebab case.\n\n  Once you've created the workflow, you should ask if you should commit the changes to the environment.\n  `,\n  parameters: z.object({\n    environment: z\n      .string()\n      .describe(\n        \"(string): The environment to create the workflow in. Defaults to `development`.\"\n      ),\n    workflowKey: z.string().describe(\"(string): The key of the workflow.\"),\n    name: z.string().describe(\"(string): The name of the workflow.\"),\n    categories: z\n      .array(z.string())\n      .describe(\"(array): The categories to add to the workflow.\"),\n    subject: z.string().describe(\"(string): The subject of the email.\"),\n    body: z.string().describe(\"(string): The body of the email.\"),\n  }),\n  execute: (knockClient, config) => async (params) => {\n    const emailChannelsPage = await knockClient.channels.list();\n    const emailChannels = emailChannelsPage.entries.filter(\n      (channel) => channel.type === \"email\"\n    );\n\n    if (emailChannels.length === 0) {\n      throw new Error(\"No email channels found\");\n    }\n\n    const workflowParams: WorkflowUpsertParams = {\n      environment: params.environment ?? config.environment ?? \"development\",\n      workflow: {\n        name: params.name,\n        categories: params.categories ?? [],\n        steps: [\n          {\n            type: \"channel\",\n            channel_key: emailChannels[0].key,\n            template: {\n              settings: {\n                layout_key: \"default\",\n              },\n              subject: params.subject,\n              visual_blocks: [\n                // @ts-ignore\n                {\n                  type: \"markdown\",\n                  content: params.body,\n                },\n              ],\n            },\n            name: \"Email\",\n            ref: \"email_1\",\n          },\n        ],\n      },\n    };\n\n    return await knockClient.workflows.upsert(\n      params.workflowKey,\n      workflowParams\n    );\n  },\n});\n\nconst createOneOffWorkflowSchedule = KnockTool({\n  method: \"create_one_off_workflow_schedule\",\n  name: \"Create one-off workflow schedule\",\n  description: `\n  Create a one-off workflow schedule for a user. Use this tool when you need to schedule the execution of a workflow for a specific user in the future, like to power a delayed notification.\n  \n  Schedules can accept a set of data that will be passed to the workflow trigger when it is executed. When the userId is not provided, the schedule will be created for the current user specified in the config.\n\n  Examples:\n  \n  - In three days, send a welcome email to a user\n  - In one hour, send a password reset email to a user\n  - In two weeks, send a survey to a user\n  `,\n  parameters: z.object({\n    workflowKey: z\n      .string()\n      .describe(\"(string): The key of the workflow to schedule.\"),\n    userId: z\n      .string()\n      .describe(\n        \"(string): The userId of the user to schedule the workflow for.\"\n      ),\n    scheduledAt: z\n      .string()\n      .describe(\n        \"(string): The date and time to schedule the workflow for. Must be in ISO 8601 format.\"\n      ),\n    data: z\n      .record(z.string(), z.any())\n      .describe(\"(object): Data to pass to the workflow.\"),\n  }),\n  execute: (knockClient, config) => async (params) => {\n    const publicClient = await knockClient.publicApi();\n\n    return await publicClient.workflows.createSchedules(params.workflowKey, {\n      recipients: [params.userId ?? config.userId],\n      scheduled_at: params.scheduledAt,\n      data: params.data,\n    });\n  },\n});\n\nexport const workflows = {\n  listWorkflows,\n  triggerWorkflow,\n  createEmailWorkflow,\n  createOneOffWorkflowSchedule,\n};\n\nexport const permissions = {\n  read: [\"listWorkflows\"],\n  manage: [\"createEmailWorkflow\", \"createOneOffWorkflowSchedule\"],\n  trigger: [\"triggerWorkflow\"],\n};\n","import type { ZodObject } from \"zod\";\nimport { z } from \"zod\";\nimport { Config } from \"../types.js\";\nimport { KnockClient } from \"./knock-client.js\";\n\nexport interface KnockToolDefinition {\n  /**\n   * The method name of the tool. This is a machine-readable string.\n   */\n  method: string;\n  /**\n   * The name of the tool. This can be used to reference the tool in the code.\n   * A descriptive LLM-readable string.\n   */\n  name: string;\n\n  /**\n   * A descriptive prompt explaining the tool's purpose, including examples where useful.\n   */\n  description: string;\n\n  /**\n   * A descriptive prompt explaining the tool's purpose, usage and input parameters.\n   * Ths is intended to be used by the underlying LLM.\n   */\n  fullDescription: string;\n\n  /**\n   * The Zod schema for the input parameters of the tool\n   */\n  parameters?: ZodObject<any>;\n  /**\n   * The actual implementation of the tool.\n   */\n  execute: (\n    knockClient: KnockClient,\n    config: Config\n  ) => (input: any) => Promise<unknown>;\n}\n\nexport interface KnockTool extends Omit<KnockToolDefinition, \"execute\"> {\n  bindExecute: (\n    knockClient: KnockClient,\n    config: Config\n  ) => (input: any) => Promise<unknown>;\n}\n\nconst trimLines = (text: string) =>\n  text\n    .split(\"\\n\")\n    .map((l) => l.trim())\n    .filter(Boolean)\n    .join(\"\\n\");\n\nexport const KnockTool = (\n  args: Omit<KnockToolDefinition, \"fullDescription\">\n): KnockTool => {\n  const { execute, ...restOfArgs } = args;\n  const parameters = restOfArgs.parameters\n    ? restOfArgs.parameters\n    : z.object({});\n\n  const schemaEntries = Object.entries(parameters.shape);\n\n  const argsStr =\n    schemaEntries.length === 0\n      ? \"Takes no arguments\"\n      : schemaEntries\n          .map(([key, value]) => {\n            return `- ${key}: ${(value as any).description || \"\"}`;\n          })\n          .join(\"\\n\");\n\n  const fullDescription = trimLines(`\n  Tool name:\n  ${args.name}\n  Description:\n  ${args.description}.\n  Arguments:\n  ${argsStr}\n  `);\n\n  return {\n    ...restOfArgs,\n    parameters,\n    fullDescription,\n    bindExecute: (knockClient: KnockClient, config: Config) =>\n      execute(knockClient, config),\n  };\n};\n"],"mappings":";AAAA,SAAS,KAAAA,UAAS;;;ACClB,SAAS,SAAS;AA8ClB,IAAM,YAAY,CAAC,SACjB,KACG,MAAM,IAAI,EACV,IAAI,CAAC,MAAM,EAAE,KAAK,CAAC,EACnB,OAAO,OAAO,EACd,KAAK,IAAI;AAEP,IAAM,YAAY,CACvB,SACc;AACd,QAAM,EAAE,SAAS,GAAG,WAAW,IAAI;AACnC,QAAM,aAAa,WAAW,aAC1B,WAAW,aACX,EAAE,OAAO,CAAC,CAAC;AAEf,QAAM,gBAAgB,OAAO,QAAQ,WAAW,KAAK;AAErD,QAAM,UACJ,cAAc,WAAW,IACrB,uBACA,cACG,IAAI,CAAC,CAAC,KAAK,KAAK,MAAM;AACrB,WAAO,KAAK,GAAG,KAAM,MAAc,eAAe,EAAE;AAAA,EACtD,CAAC,EACA,KAAK,IAAI;AAElB,QAAM,kBAAkB,UAAU;AAAA;AAAA,IAEhC,KAAK,IAAI;AAAA;AAAA,IAET,KAAK,WAAW;AAAA;AAAA,IAEhB,OAAO;AAAA,GACR;AAED,SAAO;AAAA,IACL,GAAG;AAAA,IACH;AAAA,IACA;AAAA,IACA,aAAa,CAAC,aAA0B,WACtC,QAAQ,aAAa,MAAM;AAAA,EAC/B;AACF;;;ADlFA,IAAM,gBAAgB,UAAU;AAAA,EAC9B,QAAQ;AAAA,EACR,MAAM;AAAA,EACN,aAAa;AAAA;AAAA;AAAA;AAAA;AAAA,EAKb,YAAYC,GAAE,OAAO;AAAA,IACnB,aAAaA,GACV,OAAO,EACP;AAAA,MACC;AAAA,IACF;AAAA,EACJ,CAAC;AAAA,EACD,SAAS,CAAC,aAAa,WAAW,OAAO,WAAW;AAClD,UAAM,eAA2B,CAAC;AAClC,UAAM,aAAa;AAAA,MACjB,aAAa,OAAO,eAAe,OAAO,eAAe;AAAA,IAC3D;AAEA,qBAAiB,YAAY,YAAY,UAAU,KAAK,UAAU,GAAG;AACnE,mBAAa,KAAK,QAAQ;AAAA,IAC5B;AACA,WAAO;AAAA,EACT;AACF,CAAC;AAED,IAAM,kBAAkB,UAAU;AAAA,EAChC,QAAQ;AAAA,EACR,MAAM;AAAA,EACN,aAAa;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAOb,YAAYA,GAAE,OAAO;AAAA,IACnB,aAAaA,GACV,OAAO,EACP,SAAS,+CAA+C;AAAA,IAC3D,YAAYA,GACT,MAAMA,GAAE,OAAO,CAAC,EAChB,SAAS,sDAAsD;AAAA,IAClE,MAAMA,GACH,OAAOA,GAAE,OAAO,GAAGA,GAAE,IAAI,CAAC,EAC1B,SAAS,yCAAyC;AAAA,IACrD,QAAQA,GACL,OAAOA,GAAE,OAAO,GAAGA,GAAE,IAAI,CAAC,EAC1B;AAAA,MACC;AAAA,IACF;AAAA,EACJ,CAAC;AAAA,EACD,SAAS,CAAC,aAAa,WAAW,OAAO,WAAW;AAClD,UAAM,eAAe,MAAM,YAAY,UAAU;AAEjD,UAAM,SAAS,MAAM,aAAa,UAAU,QAAQ,OAAO,aAAa;AAAA,MACtE,YAAY,OAAO;AAAA,MACnB,MAAM,OAAO;AAAA,MACb,QAAQ,OAAO;AAAA,IACjB,CAAC;AAED,WAAO,OAAO;AAAA,EAChB;AACF,CAAC;AAED,IAAM,sBAAsB,UAAU;AAAA,EACpC,QAAQ;AAAA,EACR,MAAM;AAAA,EACN,aAAa;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAqBb,YAAYA,GAAE,OAAO;AAAA,IACnB,aAAaA,GACV,OAAO,EACP;AAAA,MACC;AAAA,IACF;AAAA,IACF,aAAaA,GAAE,OAAO,EAAE,SAAS,oCAAoC;AAAA,IACrE,MAAMA,GAAE,OAAO,EAAE,SAAS,qCAAqC;AAAA,IAC/D,YAAYA,GACT,MAAMA,GAAE,OAAO,CAAC,EAChB,SAAS,iDAAiD;AAAA,IAC7D,SAASA,GAAE,OAAO,EAAE,SAAS,qCAAqC;AAAA,IAClE,MAAMA,GAAE,OAAO,EAAE,SAAS,kCAAkC;AAAA,EAC9D,CAAC;AAAA,EACD,SAAS,CAAC,aAAa,WAAW,OAAO,WAAW;AAClD,UAAM,oBAAoB,MAAM,YAAY,SAAS,KAAK;AAC1D,UAAM,gBAAgB,kBAAkB,QAAQ;AAAA,MAC9C,CAAC,YAAY,QAAQ,SAAS;AAAA,IAChC;AAEA,QAAI,cAAc,WAAW,GAAG;AAC9B,YAAM,IAAI,MAAM,yBAAyB;AAAA,IAC3C;AAEA,UAAM,iBAAuC;AAAA,MAC3C,aAAa,OAAO,eAAe,OAAO,eAAe;AAAA,MACzD,UAAU;AAAA,QACR,MAAM,OAAO;AAAA,QACb,YAAY,OAAO,cAAc,CAAC;AAAA,QAClC,OAAO;AAAA,UACL;AAAA,YACE,MAAM;AAAA,YACN,aAAa,cAAc,CAAC,EAAE;AAAA,YAC9B,UAAU;AAAA,cACR,UAAU;AAAA,gBACR,YAAY;AAAA,cACd;AAAA,cACA,SAAS,OAAO;AAAA,cAChB,eAAe;AAAA;AAAA,gBAEb;AAAA,kBACE,MAAM;AAAA,kBACN,SAAS,OAAO;AAAA,gBAClB;AAAA,cACF;AAAA,YACF;AAAA,YACA,MAAM;AAAA,YACN,KAAK;AAAA,UACP;AAAA,QACF;AAAA,MACF;AAAA,IACF;AAEA,WAAO,MAAM,YAAY,UAAU;AAAA,MACjC,OAAO;AAAA,MACP;AAAA,IACF;AAAA,EACF;AACF,CAAC;AAED,IAAM,+BAA+B,UAAU;AAAA,EAC7C,QAAQ;AAAA,EACR,MAAM;AAAA,EACN,aAAa;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAWb,YAAYA,GAAE,OAAO;AAAA,IACnB,aAAaA,GACV,OAAO,EACP,SAAS,gDAAgD;AAAA,IAC5D,QAAQA,GACL,OAAO,EACP;AAAA,MACC;AAAA,IACF;AAAA,IACF,aAAaA,GACV,OAAO,EACP;AAAA,MACC;AAAA,IACF;AAAA,IACF,MAAMA,GACH,OAAOA,GAAE,OAAO,GAAGA,GAAE,IAAI,CAAC,EAC1B,SAAS,yCAAyC;AAAA,EACvD,CAAC;AAAA,EACD,SAAS,CAAC,aAAa,WAAW,OAAO,WAAW;AAClD,UAAM,eAAe,MAAM,YAAY,UAAU;AAEjD,WAAO,MAAM,aAAa,UAAU,gBAAgB,OAAO,aAAa;AAAA,MACtE,YAAY,CAAC,OAAO,UAAU,OAAO,MAAM;AAAA,MAC3C,cAAc,OAAO;AAAA,MACrB,MAAM,OAAO;AAAA,IACf,CAAC;AAAA,EACH;AACF,CAAC;AAEM,IAAM,YAAY;AAAA,EACvB;AAAA,EACA;AAAA,EACA;AAAA,EACA;AACF;AAEO,IAAM,cAAc;AAAA,EACzB,MAAM,CAAC,eAAe;AAAA,EACtB,QAAQ,CAAC,uBAAuB,8BAA8B;AAAA,EAC9D,SAAS,CAAC,iBAAiB;AAC7B;","names":["z","z"]}
+{"version":3,"sources":[],"sourcesContent":[],"mappings":"","names":[]}