@lightdash/common 3.213.3 → 3.214.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/cjs/.tsbuildinfo +1 -1
- package/dist/cjs/authorization/jwtAbility.d.ts.map +1 -1
- package/dist/cjs/authorization/jwtAbility.js +18 -0
- package/dist/cjs/authorization/jwtAbility.js.map +1 -1
- package/dist/cjs/authorization/scopes.js +2 -2
- package/dist/cjs/authorization/scopes.js.map +1 -1
- package/dist/cjs/ee/AiAgent/composerChartVizConfig.d.ts +1 -0
- package/dist/cjs/ee/AiAgent/composerChartVizConfig.d.ts.map +1 -1
- package/dist/cjs/ee/AiAgent/composerChartVizConfig.js +6 -1
- package/dist/cjs/ee/AiAgent/composerChartVizConfig.js.map +1 -1
- package/dist/cjs/ee/AiAgent/schemas/tools/toolComposerQueryArgs.d.ts.map +1 -1
- package/dist/cjs/ee/AiAgent/schemas/tools/toolComposerQueryArgs.js +3 -1
- package/dist/cjs/ee/AiAgent/schemas/tools/toolComposerQueryArgs.js.map +1 -1
- package/dist/cjs/ee/AiAgent/schemas/tools/toolVisualizeArgs.d.ts +1 -1
- package/dist/cjs/ee/AiAgent/schemas/tools/toolVisualizeArgs.d.ts.map +1 -1
- package/dist/cjs/ee/AiAgent/schemas/tools/toolVisualizeArgs.js +2 -0
- package/dist/cjs/ee/AiAgent/schemas/tools/toolVisualizeArgs.js.map +1 -1
- package/dist/cjs/schemas/json/mcp-tools-1.0.json +1 -1
- package/dist/esm/.tsbuildinfo +1 -1
- package/dist/esm/authorization/jwtAbility.d.ts.map +1 -1
- package/dist/esm/authorization/jwtAbility.js +18 -0
- package/dist/esm/authorization/jwtAbility.js.map +1 -1
- package/dist/esm/authorization/scopes.js +2 -2
- package/dist/esm/authorization/scopes.js.map +1 -1
- package/dist/esm/ee/AiAgent/composerChartVizConfig.d.ts +1 -0
- package/dist/esm/ee/AiAgent/composerChartVizConfig.d.ts.map +1 -1
- package/dist/esm/ee/AiAgent/composerChartVizConfig.js +5 -0
- package/dist/esm/ee/AiAgent/composerChartVizConfig.js.map +1 -1
- package/dist/esm/ee/AiAgent/schemas/tools/toolComposerQueryArgs.d.ts.map +1 -1
- package/dist/esm/ee/AiAgent/schemas/tools/toolComposerQueryArgs.js +3 -1
- package/dist/esm/ee/AiAgent/schemas/tools/toolComposerQueryArgs.js.map +1 -1
- package/dist/esm/ee/AiAgent/schemas/tools/toolVisualizeArgs.d.ts +1 -1
- package/dist/esm/ee/AiAgent/schemas/tools/toolVisualizeArgs.d.ts.map +1 -1
- package/dist/esm/ee/AiAgent/schemas/tools/toolVisualizeArgs.js +2 -0
- package/dist/esm/ee/AiAgent/schemas/tools/toolVisualizeArgs.js.map +1 -1
- package/dist/esm/schemas/json/mcp-tools-1.0.json +1 -1
- package/dist/types/.tsbuildinfo +1 -1
- package/dist/types/authorization/jwtAbility.d.ts.map +1 -1
- package/dist/types/authorization/jwtAbility.js +18 -0
- package/dist/types/authorization/jwtAbility.js.map +1 -1
- package/dist/types/authorization/scopes.js +2 -2
- package/dist/types/authorization/scopes.js.map +1 -1
- package/dist/types/ee/AiAgent/composerChartVizConfig.d.ts +1 -0
- package/dist/types/ee/AiAgent/composerChartVizConfig.d.ts.map +1 -1
- package/dist/types/ee/AiAgent/composerChartVizConfig.js +5 -0
- package/dist/types/ee/AiAgent/composerChartVizConfig.js.map +1 -1
- package/dist/types/ee/AiAgent/schemas/tools/toolComposerQueryArgs.d.ts.map +1 -1
- package/dist/types/ee/AiAgent/schemas/tools/toolComposerQueryArgs.js +3 -1
- package/dist/types/ee/AiAgent/schemas/tools/toolComposerQueryArgs.js.map +1 -1
- package/dist/types/ee/AiAgent/schemas/tools/toolVisualizeArgs.d.ts +1 -1
- package/dist/types/ee/AiAgent/schemas/tools/toolVisualizeArgs.d.ts.map +1 -1
- package/dist/types/ee/AiAgent/schemas/tools/toolVisualizeArgs.js +2 -0
- package/dist/types/ee/AiAgent/schemas/tools/toolVisualizeArgs.js.map +1 -1
- package/dist/types/schemas/json/mcp-tools-1.0.json +1 -1
- package/package.json +1 -1
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
import { z } from 'zod';
|
|
2
|
-
export declare const TOOL_VISUALIZE_DESCRIPTION = "Visualize a node's result for the user as a chart or table. Each call adds one card to the thread; a result stays hidden until it is visualized.\n\nnodeId names a node from a successful query call in this thread, in this turn or an earlier one, so a result can be visualized again with a different vizConfig without rerunning query. vizConfig references are that node's result columns, as listed in its query result.\n\nShow related metrics that answer one comparison over the same x in one visualize call, unless the user asks for separate charts: same-scale metrics in y, and a metric on a different scale in y2 instead. When they need more scales than y and y2 hold, or bars and lines together, use a custom chart type whose slots fit, when the project has one. Call visualize on the same node again for a different x or chart, not once per metric.\n\nPie and series-split charts return readability notes when they have many slices or series.";
|
|
2
|
+
export declare const TOOL_VISUALIZE_DESCRIPTION = "Visualize a node's result for the user as a chart or table. Each call adds one card to the thread; a result stays hidden until it is visualized.\n\nA request to chart a single-number answer asks for the breakdown behind it: visualize the node that produced the number.\n\nnodeId names a node from a successful query call in this thread, in this turn or an earlier one, so a result can be visualized again with a different vizConfig without rerunning query. vizConfig references are that node's result columns, as listed in its query result.\n\nShow related metrics that answer one comparison over the same x in one visualize call, unless the user asks for separate charts: same-scale metrics in y, and a metric on a different scale in y2 instead. When they need more scales than y and y2 hold, or bars and lines together, use a custom chart type whose slots fit, when the project has one. Call visualize on the same node again for a different x or chart, not once per metric.\n\nPie and series-split charts return readability notes when they have many slices or series.";
|
|
3
3
|
export declare const toolVisualizeArgsSchema: z.ZodObject<{
|
|
4
4
|
nodeId: z.ZodString;
|
|
5
5
|
title: z.ZodString;
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"toolVisualizeArgs.d.ts","sourceRoot":"","sources":["../../../../../../src/ee/AiAgent/schemas/tools/toolVisualizeArgs.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAKxB,eAAO,MAAM,0BAA0B,
|
|
1
|
+
{"version":3,"file":"toolVisualizeArgs.d.ts","sourceRoot":"","sources":["../../../../../../src/ee/AiAgent/schemas/tools/toolVisualizeArgs.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAKxB,eAAO,MAAM,0BAA0B,kjCAQoD,CAAC;AAqB5F,eAAO,MAAM,uBAAuB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;iBAA4B,CAAC;AAIjE,eAAO,MAAM,gCAAgC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;iBAA4B,CAAC;AAE1E,MAAM,MAAM,iBAAiB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,uBAAuB,CAAC,CAAC;AAExE,QAAA,MAAM,kCAAkC;;;;;;iBAOtC,CAAC;AAEH,MAAM,MAAM,4BAA4B,GAAG,CAAC,CAAC,KAAK,CAC9C,OAAO,kCAAkC,CAC5C,CAAC;AAEF,eAAO,MAAM,iCAAiC,aAChC,OAAO,KAClB,4BAA4B,GAAG,IAGjC,CAAC;AAEF,eAAO,MAAM,yBAAyB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;mBAWpC,CAAC;AAEH,MAAM,MAAM,mBAAmB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,yBAAyB,CAAC,CAAC"}
|
|
@@ -4,6 +4,8 @@ import { createToolSchema } from '../toolSchemaBuilder';
|
|
|
4
4
|
import { composerChartVizConfigSchema } from './composerChartVizConfigSchema';
|
|
5
5
|
export const TOOL_VISUALIZE_DESCRIPTION = `Visualize a node's result for the user as a chart or table. Each call adds one card to the thread; a result stays hidden until it is visualized.
|
|
6
6
|
|
|
7
|
+
A request to chart a single-number answer asks for the breakdown behind it: visualize the node that produced the number.
|
|
8
|
+
|
|
7
9
|
nodeId names a node from a successful query call in this thread, in this turn or an earlier one, so a result can be visualized again with a different vizConfig without rerunning query. vizConfig references are that node's result columns, as listed in its query result.
|
|
8
10
|
|
|
9
11
|
Show related metrics that answer one comparison over the same x in one visualize call, unless the user asks for separate charts: same-scale metrics in y, and a metric on a different scale in y2 instead. When they need more scales than y and y2 hold, or bars and lines together, use a custom chart type whose slots fit, when the project has one. Call visualize on the same node again for a different x or chart, not once per metric.
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"toolVisualizeArgs.js","sourceRoot":"","sources":["../../../../../../src/ee/AiAgent/schemas/tools/toolVisualizeArgs.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,0BAA0B,EAAE,MAAM,mBAAmB,CAAC;AAC/D,OAAO,EAAE,gBAAgB,EAAE,MAAM,sBAAsB,CAAC;AACxD,OAAO,EAAE,4BAA4B,EAAE,MAAM,gCAAgC,CAAC;AAE9E,MAAM,CAAC,MAAM,0BAA0B,GAAG
|
|
1
|
+
{"version":3,"file":"toolVisualizeArgs.js","sourceRoot":"","sources":["../../../../../../src/ee/AiAgent/schemas/tools/toolVisualizeArgs.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,0BAA0B,EAAE,MAAM,mBAAmB,CAAC;AAC/D,OAAO,EAAE,gBAAgB,EAAE,MAAM,sBAAsB,CAAC;AACxD,OAAO,EAAE,4BAA4B,EAAE,MAAM,gCAAgC,CAAC;AAE9E,MAAM,CAAC,MAAM,0BAA0B,GAAG;;;;;;;;2FAQiD,CAAC;AAE5F,MAAM,yBAAyB,GAAG,gBAAgB,EAAE;KAC/C,MAAM,CAAC;IACJ,MAAM,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,oCAAoC,CAAC;IACjE,KAAK,EAAE,CAAC;SACH,MAAM,EAAE;SACR,QAAQ,CACL,oFAAoF,CACvF;IACL,WAAW,EAAE,CAAC;SACT,MAAM,EAAE;SACR,OAAO,EAAE;SACT,OAAO,CAAC,IAAI,CAAC;SACb,QAAQ,CACL,yFAAyF,CAC5F;IACL,SAAS,EAAE,4BAA4B;CAC1C,CAAC;KACD,KAAK,EAAE,CAAC;AAEb,MAAM,CAAC,MAAM,uBAAuB,GAAG,yBAAyB,CAAC;AAEjE,2EAA2E;AAC3E,wEAAwE;AACxE,MAAM,CAAC,MAAM,gCAAgC,GAAG,yBAAyB,CAAC;AAI1E,MAAM,kCAAkC,GAAG,CAAC,CAAC,MAAM,CAAC;IAChD,MAAM,EAAE,CAAC,CAAC,OAAO,CAAC,SAAS,CAAC;IAC5B,MAAM,EAAE,CAAC,CAAC,MAAM,EAAE;IAClB,YAAY,EAAE,CAAC,CAAC,MAAM,EAAE;IACxB,WAAW,EAAE,CAAC,CAAC,MAAM,EAAE;IACvB,yEAAyE;IACzE,SAAS,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE;CACnC,CAAC,CAAC;AAMH,MAAM,CAAC,MAAM,iCAAiC,GAAG,CAC7C,QAAiB,EACkB,EAAE;IACrC,MAAM,MAAM,GAAG,kCAAkC,CAAC,SAAS,CAAC,QAAQ,CAAC,CAAC;IACtE,OAAO,MAAM,CAAC,OAAO,CAAC,CAAC,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC,IAAI,CAAC;AAC/C,CAAC,CAAC;AAEF,MAAM,CAAC,MAAM,yBAAyB,GAAG,0BAA0B,CAAC;IAChE,QAAQ,EAAE,CAAC,CAAC,kBAAkB,CAAC,QAAQ,EAAE;QACrC,kCAAkC;QAClC,CAAC,CAAC,MAAM,CAAC,EAAE,MAAM,EAAE,CAAC,CAAC,OAAO,CAAC,OAAO,CAAC,EAAE,CAAC;KAC3C,CAAC;IACF,iBAAiB,EAAE,CAAC,CAAC,MAAM,CAAC;QACxB,MAAM,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,sBAAsB,CAAC;QACnD,KAAK,EAAE,CAAC;aACH,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC;aACjB,QAAQ,CAAC,kDAAkD,CAAC;KACpE,CAAC;CACL,CAAC,CAAC"}
|
|
@@ -3184,7 +3184,7 @@
|
|
|
3184
3184
|
"readOnlyHint": true,
|
|
3185
3185
|
"title": "Run composer queries"
|
|
3186
3186
|
},
|
|
3187
|
-
"description": "Run a pipeline: up to 25 nodes submitted together, where duckdb and python nodes join or transform other nodes' results. A pipeline of one node runs a single semantic-layer or SQL query.\n\nNode kinds:\n- \"semanticLayer\": a metric query against an explore. Result columns are the requested field ids.\n- \"sql\": raw SQL against the project warehouse; available only when run_sql is.\n- \"external\": DuckDB SQL over uploaded or connected tables declared in \"tables\".\n- \"duckdb\": DuckDB SQL over other results declared in \"references\".\n- \"python\": pandas code over other results declared in \"references\".\n\nA node reads only the rows its references returned, so a referenced result that reached its limit is incomplete: aggregate in the referenced node itself.\n\nA python node's \"code\" defines `def run(inputs, params)`, and semanticLayer \"filters\" are flat expression strings; each field documents its contract.\n\nReuse earlier nodes: a result returns a sessionId once a node has finished; finished nodes are saved in it. On a follow-up, pass that sessionId and read saved nodes by node id in \"references\", submitting only the new nodes. Reused nodes bring everything they read and are served from cache when possible. A saved node id names one node for the whole session, so give a changed node a new node id; a failed or unfinished node is not saved, so resubmit it under the same id. Omit sessionId to start a new session.\n\nReturns the terminal node's first rows, other submitted nodes' columns and first rows, and every node's queryUuid. If the result is running, follow up with get_query_result on each queryUuid it names; it also fetches the first page of any node's result by its queryUuid. query computes data only; it saves and charts nothing.",
|
|
3187
|
+
"description": "Run a pipeline: up to 25 nodes submitted together, where duckdb and python nodes join or transform other nodes' results. A pipeline of one node runs a single semantic-layer or SQL query.\n\nNode kinds:\n- \"semanticLayer\": a metric query against an explore. Result columns are the requested field ids.\n- \"sql\": raw SQL against the project warehouse; available only when run_sql is.\n- \"external\": DuckDB SQL over uploaded or connected tables declared in \"tables\".\n- \"duckdb\": DuckDB SQL over other results declared in \"references\".\n- \"python\": pandas code over other results declared in \"references\".\n\nA node reads only the rows its references returned, so a referenced result that reached its limit is incomplete: aggregate in the referenced node itself.\n\nA duckdb node that only reshapes another duckdb node's result (adds a column, filters, renames, re-sorts) belongs in that node's SQL: write one duckdb node over the original's references, under a new node id if the original is from an earlier call. Each duckdb step waits for the one it reads.\n\nA python node's \"code\" defines `def run(inputs, params)`, and semanticLayer \"filters\" are flat expression strings; each field documents its contract.\n\nReuse earlier nodes: a result returns a sessionId once a node has finished; finished nodes are saved in it. On a follow-up, pass that sessionId and read saved nodes by node id in \"references\", submitting only the new nodes. Reused nodes bring everything they read and are served from cache when possible. A saved node id names one node for the whole session, so give a changed node a new node id; a failed or unfinished node is not saved, so resubmit it under the same id. Omit sessionId to start a new session.\n\nReturns the terminal node's first rows, other submitted nodes' columns and first rows, and every node's queryUuid. If the result is running, follow up with get_query_result on each queryUuid it names; it also fetches the first page of any node's result by its queryUuid. query computes data only; it saves and charts nothing.",
|
|
3188
3188
|
"inputSchema": {
|
|
3189
3189
|
"$schema": "http://json-schema.org/draft-07/schema#",
|
|
3190
3190
|
"properties": {
|