drizzle-cube 0.9.6 → 0.9.7

package/dist/adapters/utils.cjs

@@ -1 +1 @@
-Object.defineProperty(exports,Symbol.toStringTag,{value:`Module`});const e=require("./utils-BFGzuSlF.cjs");exports.buildTransformedQuery=e.t,exports.calculateQueryComplexity=e.n,exports.formatCubeResponse=e.r,exports.formatErrorResponse=e.i,exports.formatMetaResponse=e.a,exports.formatSqlResponse=e.o,exports.formatSqlString=e.x,exports.generateRequestId=e.s,exports.getDatabaseType=e.c,exports.handleBatchRequest=e.l,exports.handleDiscover=e.p,exports.handleDryRun=e.u,exports.handleLoad=e.m,exports.handleSuggest=e.d,exports.handleValidate=e.f,exports.normalizeQueryFields=e.h;
+Object.defineProperty(exports,Symbol.toStringTag,{value:`Module`});const e=require("./utils-Du_UZbn5.cjs");exports.buildTransformedQuery=e.t,exports.calculateQueryComplexity=e.n,exports.formatCubeResponse=e.r,exports.formatErrorResponse=e.i,exports.formatMetaResponse=e.a,exports.formatSqlResponse=e.o,exports.formatSqlString=e.x,exports.generateRequestId=e.s,exports.getDatabaseType=e.c,exports.handleBatchRequest=e.l,exports.handleDiscover=e.p,exports.handleDryRun=e.u,exports.handleLoad=e.m,exports.handleSuggest=e.d,exports.handleValidate=e.f,exports.normalizeQueryFields=e.h;

package/dist/adapters/utils.js

@@ -1,2 +1,2 @@
-import { a as e, c as t, d as n, f as r, h as i, i as a, l as o, m as s, n as c, o as l, p as u, r as d, s as f, t as p, u as m, x as h } from "./utils-C_Mc0qsk.js";
+import { a as e, c as t, d as n, f as r, h as i, i as a, l as o, m as s, n as c, o as l, p as u, r as d, s as f, t as p, u as m, x as h } from "./utils-i2h5cwI3.js";
 export { p as buildTransformedQuery, c as calculateQueryComplexity, d as formatCubeResponse, a as formatErrorResponse, e as formatMetaResponse, l as formatSqlResponse, h as formatSqlString, f as generateRequestId, t as getDatabaseType, o as handleBatchRequest, u as handleDiscover, m as handleDryRun, s as handleLoad, n as handleSuggest, r as handleValidate, i as normalizeQueryFields };

package/dist/cjs/server/adapters/base-adapter.d.ts

@@ -103,7 +103,7 @@ export interface DatabaseAdapter {
      * @param value - The value to match
      * @returns SQL expression for string matching
      */
-    buildStringCondition(fieldExpr: AnyColumn | SQL, operator: 'contains' | 'notContains' | 'startsWith' | 'endsWith' | 'like' | 'notLike' | 'ilike' | 'regex' | 'notRegex', value: string): SQL;
+    buildStringCondition(fieldExpr: AnyColumn | SQL, operator: 'contains' | 'notContains' | 'startsWith' | 'notStartsWith' | 'endsWith' | 'notEndsWith' | 'like' | 'notLike' | 'ilike' | 'regex' | 'notRegex', value: string): SQL;
     /**
      * Cast expression to specific database type
      * @param fieldExpr - The field expression to cast
@@ -241,7 +241,7 @@ export declare abstract class BaseDatabaseAdapter implements DatabaseAdapter {
      */
     protected nullToZero(expr: SQL): SQL;
     /**
-     * Case-insensitive LIKE matching for contains/startsWith/endsWith/ilike.
+     * Case-insensitive LIKE matching for (not)contains/(not)startsWith/(not)endsWith/ilike.
      * Default uses native ILIKE (PostgreSQL/DuckDB/Snowflake); engines without ILIKE
      * (MySQL/SQLite/Databend) override with LOWER()+LIKE.
      * @param pattern - the LIKE pattern in its original case (already wrapped with % as needed)
@@ -257,7 +257,7 @@ export declare abstract class BaseDatabaseAdapter implements DatabaseAdapter {
      * delegated to the caseInsensitiveLike()/regexCondition() hooks; plain LIKE/NOT LIKE
      * are identical across all engines.
      */
-    buildStringCondition(fieldExpr: AnyColumn | SQL, operator: 'contains' | 'notContains' | 'startsWith' | 'endsWith' | 'like' | 'notLike' | 'ilike' | 'regex' | 'notRegex', value: string): SQL;
+    buildStringCondition(fieldExpr: AnyColumn | SQL, operator: 'contains' | 'notContains' | 'startsWith' | 'notStartsWith' | 'endsWith' | 'notEndsWith' | 'like' | 'notLike' | 'ilike' | 'regex' | 'notRegex', value: string): SQL;
     /**
      * Build conditional aggregation. Default uses portable CASE WHEN
      * (MySQL/SQLite/Databend/Snowflake); PostgreSQL/DuckDB override with the FILTER clause.

package/dist/cjs/server/ai/query-schema.d.ts

@@ -45,7 +45,7 @@ export declare const QUERY_PARAMS_SCHEMA: {
                 readonly values: {
                     readonly type: "array";
                     readonly items: {};
-                    readonly description: "Filter values. Omit for set/notSet/isEmpty/isNotEmpty.";
+                    readonly description: "Filter values. Omit for set/notSet/isEmpty/isNotEmpty. inDateRange: [\"last 3 months\"] (one relative string) or [\"YYYY-MM-DD\", \"YYYY-MM-DD\"].";
                 };
             };
             readonly required: readonly ["member", "operator"];
@@ -64,10 +64,10 @@ export declare const QUERY_PARAMS_SCHEMA: {
                 readonly granularity: {
                     readonly type: "string";
                     readonly enum: readonly ["second", "minute", "hour", "day", "week", "month", "quarter", "year"];
-                    readonly description: "Time bucket size. REQUIRED for time series; omit only for date range filtering.";
+                    readonly description: "Time bucket size. REQUIRED for time series. Without it the time dimension is a date-range filter only (no time column, no grouping).";
                 };
                 readonly dateRange: {
-                    readonly description: "Relative string (\"last 7 days\", \"this month\", \"last quarter\") or absolute tuple [\"YYYY-MM-DD\", \"YYYY-MM-DD\"]";
+                    readonly description: "Relative string (\"today\", \"last 7 days\", \"this month\", \"last quarter\", \"next week\", \"last N days|weeks|months|quarters|years\"), a single \"YYYY-MM-DD\", or absolute tuple [\"YYYY-MM-DD\", \"YYYY-MM-DD\"]. Unrecognised strings are rejected.";
                 };
                 readonly fillMissingDates: {
                     readonly type: "boolean";

package/dist/cjs/server/builders/date-time-builder.d.ts

@@ -18,8 +18,7 @@ export declare class DateTimeBuilder {
     private buildArrayDateRangeCondition;
     private buildStringDateRangeCondition;
     /**
-     * Parse relative date range expressions like "today", "yesterday", "last 7 days", "this month", etc.
-     * Handles all 14 DATE_RANGE_OPTIONS from the client
+     * Parse relative date range expressions like "today", "yesterday", "last 7 days", "this month", "next week", etc.
      */
     parseRelativeDateRange(dateRange: string): {
         start: Date;

package/dist/cjs/server/builders/date-time-helpers.d.ts

@@ -22,13 +22,26 @@ export declare function isDateOnlyString(value: unknown): value is string;
  * unparseable.
  */
 export declare function normalizeDateValue(databaseAdapter: DatabaseAdapter, value: any): string | number | null;
-type DateRange = {
+/**
+ * Parse relative date range expressions like "today", "yesterday",
+ * "last 7 days", "this month", "next week", etc. Delegates to the shared parser
+ * so the server, gap filler and client resolve the same strings identically.
+ */
+export declare function parseRelativeDateRangeValue(dateRange: string): {
     start: Date;
     end: Date;
-};
+} | null;
 /**
- * Parse relative date range expressions like "today", "yesterday",
- * "last 7 days", "this month", etc. Handles all 14 DATE_RANGE_OPTIONS.
+ * Whether a value parses as a single absolute date (string, number or Date) —
+ * the same test `normalizeDateValue` applies before building SQL.
+ */
+export declare function isValidDateValue(value: unknown): boolean;
+/**
+ * Whether a date-range expression resolves to concrete bounds exactly as
+ * `DateTimeBuilder.buildDateRangeCondition` would resolve it:
+ * - a relative string ('last 7 days', 'this month', 'next week', ...)
+ * - a single absolute date string (that whole day)
+ * - a one-element array holding either of the above
+ * - a `[start, end]` pair of absolute dates
  */
-export declare function parseRelativeDateRangeValue(dateRange: string): DateRange | null;
-export {};
+export declare function isResolvableDateRange(dateRange: unknown): boolean;

package/dist/cjs/server/builders/filter-operators.d.ts

@@ -16,8 +16,17 @@ export interface FilterOperatorContext {
     databaseAdapter: DatabaseAdapter;
     dateTimeBuilder: DateTimeBuilder;
 }
+/** Every operator the SQL layer can build, in declaration order. */
+export declare const SUPPORTED_FILTER_OPERATORS: FilterOperator[];
+/** Type guard: whether `operator` is a filter operator the SQL layer can build. */
+export declare function isSupportedFilterOperator(operator: unknown): operator is FilterOperator;
+/**
+ * Operators that test the field itself and take no values (`values` may be
+ * omitted or empty).
+ */
+export declare const NO_VALUE_FILTER_OPERATORS: ReadonlySet<FilterOperator>;
 /**
  * Dispatch a single filter operator to its handler. Returns null for any
- * unknown operator (matching the original `default` case).
+ * unknown operator (validation rejects those before SQL is built).
  */
 export declare function applyFilterOperator(operator: FilterOperator, ctx: FilterOperatorContext): SQL | null;

package/dist/cjs/server/execution/query-normalizer.d.ts

@@ -0,0 +1,9 @@
+import { SemanticQuery, TimeDimension } from '../types/index.js';
+/** Whether a timeDimension only restricts the date range (no granularity, no comparison). */
+export declare function isFilterOnlyTimeDimension(timeDimension: TimeDimension): boolean;
+/**
+ * Rewrite granularity-less timeDimensions into equivalent `inDateRange`
+ * filters, dropping them from the selection. Returns the query unchanged when
+ * there is nothing to rewrite.
+ */
+export declare function normalizeFilterOnlyTimeDimensions(query: SemanticQuery): SemanticQuery;

package/dist/cjs/server/physical-plan/drizzle-sql-builder.d.ts

@@ -73,6 +73,31 @@ export declare class DrizzleSqlBuilder {
      * @param filterType - 'where' for dimension filters, 'having' for measure filters
      */
     private processFilter;
+    /** Whether a cube's rows are directly addressable in this WHERE clause. */
+    private isCubeInScope;
+    /**
+     * An OR group needs semi-join rewriting when it references several cubes and
+     * some — but not all — of them are in scope. (All in scope: plain OR. None in
+     * scope: the group belongs entirely to another clause, e.g. inside a CTE.)
+     */
+    private orNeedsSemiJoins;
+    /**
+     * Build a logical filter where in-scope leaves are plain conditions and
+     * out-of-scope leaves become `inScopeKey IN (SELECT key FROM leafCube WHERE
+     * security AND leaf)`. This keeps OR semantics exact across a CTE boundary.
+     */
+    private buildFilterWithSemiJoins;
+    /** Rewrite one out-of-scope leaf as a semi-join onto an in-scope cube. */
+    private buildSemiJoinLeaf;
+    /** Every cube visible from here: the in-scope map plus the rest of the plan. */
+    private knownCubes;
+    /**
+     * Find how an out-of-scope cube links to the rows in scope, as a list of
+     * semi-join hops ordered outward from an in-scope cube (the last hop's cube is
+     * the leaf's cube). A pre-aggregated cube links through its CTE join keys;
+     * anything else through the shortest equi-join path (no many-to-many hops).
+     */
+    private findSemiJoinPath;
     /** Build a WHERE condition for a dimension filter, honouring CTE skips and the filter cache. */
     private processWhereDimensionFilter;
     /**

package/dist/cjs/server/physical-plan/semi-join.d.ts

@@ -0,0 +1,21 @@
+import { SQL, AnyColumn } from 'drizzle-orm';
+import { BaseQueryDefinition, QueryContext } from '../types/index.js';
+/** One key pair linking the outer query's column to the subquery cube's column. */
+export interface SemiJoinKeyPair {
+    /** Column already in scope in the outer query */
+    outer: AnyColumn;
+    /** Column on the subquery cube's table */
+    inner: AnyColumn;
+}
+/**
+ * Apply a cube's BaseQueryDefinition.joins (intra-cube table-level joins)
+ * to a Drizzle query/subquery built from cubeBase.from, so joined-table columns
+ * are in scope for SELECTs and WHEREs.
+ */
+export declare function applyBaseJoins(query: any, cubeBase: Pick<BaseQueryDefinition, 'joins'>): any;
+/**
+ * Build `outer IN (SELECT inner FROM cube WHERE conditions)` for a single key,
+ * or `EXISTS (SELECT 1 FROM cube WHERE inner = outer AND ... AND conditions)`
+ * for composite keys (portable across all engines).
+ */
+export declare function buildSemiJoinCondition(context: QueryContext, cubeBase: BaseQueryDefinition, keyPairs: SemiJoinKeyPair[], conditions: SQL[]): SQL;

package/dist/cjs/server/prompts/single-step-prompt.d.ts

@@ -20,7 +20,7 @@
  * - {CUBE_SCHEMA} - JSON-formatted cube schema
  * - {USER_PROMPT} - User's natural language query
  */
-export declare const SYSTEM_PROMPT_TEMPLATE = "You are a helpful AI assistant for analyzing business data using Cube.js/Drizzle-Cube semantic layer.\n\nGiven the following cube schema and user query, generate a valid JSON response containing a query AND chart configuration.\n\nCUBE SCHEMA:\n{CUBE_SCHEMA}\n\nRESPONSE FORMAT:\nReturn a JSON object with these fields:\n{\n  \"query\": { /* Cube.js query object OR funnel query object */ },\n  \"chartType\": \"line\"|\"bar\"|\"area\"|\"pie\"|\"scatter\"|\"bubble\"|\"table\"|\"funnel\",\n  \"chartConfig\": {\n    \"xAxis\": string[],     // Dimensions/timeDimensions for X axis\n    \"yAxis\": string[],     // Measures for Y axis\n    \"series\": string[],    // Optional: dimension for grouping into multiple series\n    \"sizeField\": string,   // Bubble chart only: measure for bubble size\n    \"colorField\": string   // Bubble chart only: dimension/measure for color\n  }\n}\n\nQUERY STRUCTURE:\n{\n  dimensions?: string[], // dimension names from CUBE SCHEMA\n  measures?: string[], // measure names from CUBE SCHEMA\n  timeDimensions?: [{\n    dimension: string, // time dimension from CUBE SCHEMA\n    granularity?: 'second'|'minute'|'hour'|'day'|'week'|'month'|'quarter'|'year',\n    dateRange?: [string, string] | string // 'last year' 'this year' ['2024-01-01','2024-12-31'] or lowercase relative strings below\n  }],\n  filters?: [{\n    member: string, // dimension/measure from CUBE SCHEMA\n    operator: 'equals'|'notEquals'|'contains'|'notContains'|'startsWith'|'endsWith'|'gt'|'gte'|'lt'|'lte'|'inDateRange'|'notInDateRange'|'beforeDate'|'afterDate'|'set'|'notSet',\n    values?: any[] // required unless set/notSet\n  }],\n  order?: {[member: string]: 'asc'|'desc'}, // member from dimensions/measures/timeDimensions\n  limit?: number,\n  offset?: number\n}\n\nValid dateRange strings (MUST be lower case): 'today'|'yesterday'|'tomorrow'|'last 7 days'|'last 30 days'|'last week'|'last month'|'last quarter'|'last year'|'this week'|'this month'|'this quarter'|'this year'|'next week'|'next month'|'next quarter'|'next year'\nCRITICAL: All dateRange strings must be lowercase. Never capitalize (e.g., use 'last 7 days' NOT 'Last 7 days').\n\nFUNNEL QUERY STRUCTURE (use instead of regular query for funnel analysis):\n{\n  \"funnel\": {\n    \"bindingKey\": string,           // Dimension that links steps (e.g., \"Events.userId\")\n    \"timeDimension\": string,        // Time dimension for ordering (e.g., \"Events.timestamp\")\n    \"steps\": [\n      {\n        \"name\": string,             // Step display name (e.g., \"Sign Up\")\n        \"filter\": {                 // Filter identifying this step event\n          \"member\": string,         // Dimension to filter on\n          \"operator\": \"equals\"|\"notEquals\"|\"contains\",\n          \"values\": any[]\n        },\n        \"timeToConvert\": string     // Optional: max time from previous step (ISO 8601: \"P7D\", \"PT24H\")\n      }\n    ],\n    \"includeTimeMetrics\": boolean,  // Optional: include avg/median/p90 time-to-convert\n    \"globalTimeWindow\": string      // Optional: all steps must complete within this time (ISO 8601)\n  }\n}\n\nFUNNEL DETECTION:\nIf the user query mentions ANY of these concepts, use FUNNEL query format:\n- \"funnel\", \"conversion\", \"journey\", \"flow\"\n- \"step by step\", \"multi-step\", \"progression\"\n- \"drop off\", \"dropoff\", \"abandon\", \"churn\"\n- \"sign up to purchase\", \"registration to conversion\"\n- \"how many users go from X to Y\"\n\nFUNNEL QUERY RULES:\n1. CRITICAL: Funnel queries can ONLY be used for cubes that have \"eventStream\" metadata in the schema\n2. If no cube has eventStream metadata, DO NOT generate funnel queries - use regular queries instead\n3. Use \"funnel\" chart type when generating funnel queries\n4. bindingKey should match the eventStream.bindingKey from the cube metadata\n5. timeDimension should match the eventStream.timeDimension from the cube metadata\n6. Each step needs a name and filter that identifies that event\n7. Steps are ordered - step 2 must occur after step 1\n8. timeToConvert is optional but useful (e.g., \"P7D\" = 7 days, \"PT24H\" = 24 hours)\n9. ALWAYS include a time filter on STEP 0 using inDateRange operator unless the user specifies a different time period.\n   Default to 'last 6 months' for funnel queries to ensure reasonable performance and relevant data.\n   Add this as an additional filter in the first step's filter array.\n   Example: step 0 filter should include: { \"member\": \"PREvents.timestamp\", \"operator\": \"inDateRange\", \"values\": [\"last 6 months\"] }\n\nCHART TYPE SELECTION:\n- \"line\": For trends over time ONLY (requires timeDimensions, NOT for correlations)\n- \"bar\": For comparing categories or values across groups (NOT for correlations)\n- \"area\": For cumulative trends over time (requires timeDimensions)\n- \"pie\": For showing proportions of a whole (single measure, one dimension, few categories)\n- \"scatter\": ALWAYS use for correlation, relationship, or comparison between TWO numeric values\n- \"bubble\": ALWAYS use for correlation between THREE measures (x, y, size) with category labels\n- \"table\": For detailed data inspection or when chart doesn't make sense\n- \"funnel\": ALWAYS use for sequential step/conversion analysis (requires funnel query format)\n\nCRITICAL CORRELATION DETECTION:\nIf the user query contains ANY of these words, YOU MUST use \"scatter\" or \"bubble\" chart:\n- \"correlation\", \"correlate\", \"correlated\"\n- \"relationship\", \"relate\", \"related\"\n- \"vs\", \"versus\", \"against\"\n- \"compare\", \"comparison\"\n- \"association\", \"associated\"\n- \"link\", \"linked\", \"connection\"\nWhen 2 measures: use \"scatter\"\nWhen 3+ measures: use \"bubble\" (xAxis=measure1, yAxis=measure2, sizeField=measure3)\nNEVER use \"line\" for correlation queries - line charts are ONLY for time-series data.\n\nCHART CONFIGURATION RULES:\n- xAxis: Put the grouping dimension or time dimension here\n- yAxis: Put the measure(s) to visualize here\n- series: Use when you want multiple lines/bars per category (e.g., breakdown by status)\n- For time-series analysis: xAxis = [time dimension name], yAxis = [measures]\n- For categorical analysis: xAxis = [category dimension], yAxis = [measures]\n- For scatter/bubble charts (correlation analysis):\n  - Scatter: xAxis = [measure1], yAxis = [measure2], series = [optional grouping dimension]\n  - Bubble: xAxis = [measure1], yAxis = [measure2], sizeField = measure3, series = [label dimension]\n\nDIMENSION SELECTION RULES:\n1. ALWAYS prefer .name fields over .id fields (e.g., use \"Employees.name\" NOT \"Employees.id\")\n2. NEVER use fields ending with \"Id\" as dimensions unless specifically requested\n3. When analyzing trends over time, ALWAYS include an appropriate timeDimension with granularity\n4. For \"by\" queries (e.g., \"sales by region\"), use the category as the xAxis dimension\n5. Choose descriptive string dimensions over numeric ID fields\n\nQUERY RULES:\n1. Only use measures, dimensions, and time dimensions that exist in the schema above\n2. Return ONLY valid JSON - no explanations or markdown\n3. Use proper Cube.js query format with measures, dimensions, timeDimensions, filters, etc.\n4. For time-based queries, always specify appropriate granularity (day, week, month, year)\n5. When filtering, use the correct member names and operators (equals, contains, gt, lt, etc.)\n6. At least one measure or dimension is required\n\nUSER QUERY:\n{USER_PROMPT}\n\nReturn the JSON response:";
+export declare const SYSTEM_PROMPT_TEMPLATE = "You are a helpful AI assistant for analyzing business data using Cube.js/Drizzle-Cube semantic layer.\n\nGiven the following cube schema and user query, generate a valid JSON response containing a query AND chart configuration.\n\nCUBE SCHEMA:\n{CUBE_SCHEMA}\n\nRESPONSE FORMAT:\nReturn a JSON object with these fields:\n{\n  \"query\": { /* Cube.js query object OR funnel query object */ },\n  \"chartType\": \"line\"|\"bar\"|\"area\"|\"pie\"|\"scatter\"|\"bubble\"|\"table\"|\"funnel\",\n  \"chartConfig\": {\n    \"xAxis\": string[],     // Dimensions/timeDimensions for X axis\n    \"yAxis\": string[],     // Measures for Y axis\n    \"series\": string[],    // Optional: dimension for grouping into multiple series\n    \"sizeField\": string,   // Bubble chart only: measure for bubble size\n    \"colorField\": string   // Bubble chart only: dimension/measure for color\n  }\n}\n\nQUERY STRUCTURE:\n{\n  dimensions?: string[], // dimension names from CUBE SCHEMA\n  measures?: string[], // measure names from CUBE SCHEMA\n  timeDimensions?: [{\n    dimension: string, // time dimension from CUBE SCHEMA\n    granularity?: 'second'|'minute'|'hour'|'day'|'week'|'month'|'quarter'|'year',\n    dateRange?: [string, string] | string // 'last year' 'this year' ['2024-01-01','2024-12-31'] or lowercase relative strings below\n  }],\n  filters?: [{\n    member: string, // dimension/measure from CUBE SCHEMA\n    operator: 'equals'|'notEquals'|'contains'|'notContains'|'startsWith'|'notStartsWith'|'endsWith'|'notEndsWith'|'gt'|'gte'|'lt'|'lte'|'in'|'notIn'|'inDateRange'|'beforeDate'|'afterDate'|'set'|'notSet'|'isEmpty'|'isNotEmpty',\n    values?: any[] // required unless set/notSet/isEmpty/isNotEmpty; inDateRange: ['last 7 days'] or ['2024-01-01','2024-03-31']\n  }],\n  order?: {[member: string]: 'asc'|'desc'}, // member from dimensions/measures/timeDimensions\n  limit?: number,\n  offset?: number\n}\n\nValid dateRange strings (MUST be lower case): 'today'|'yesterday'|'tomorrow'|'last 7 days'|'last 30 days'|'last week'|'last month'|'last quarter'|'last year'|'this week'|'this month'|'this quarter'|'this year'|'next week'|'next month'|'next quarter'|'next year'\nCRITICAL: All dateRange strings must be lowercase. Never capitalize (e.g., use 'last 7 days' NOT 'Last 7 days').\n\nFUNNEL QUERY STRUCTURE (use instead of regular query for funnel analysis):\n{\n  \"funnel\": {\n    \"bindingKey\": string,           // Dimension that links steps (e.g., \"Events.userId\")\n    \"timeDimension\": string,        // Time dimension for ordering (e.g., \"Events.timestamp\")\n    \"steps\": [\n      {\n        \"name\": string,             // Step display name (e.g., \"Sign Up\")\n        \"filter\": {                 // Filter identifying this step event\n          \"member\": string,         // Dimension to filter on\n          \"operator\": \"equals\"|\"notEquals\"|\"contains\",\n          \"values\": any[]\n        },\n        \"timeToConvert\": string     // Optional: max time from previous step (ISO 8601: \"P7D\", \"PT24H\")\n      }\n    ],\n    \"includeTimeMetrics\": boolean,  // Optional: include avg/median/p90 time-to-convert\n    \"globalTimeWindow\": string      // Optional: all steps must complete within this time (ISO 8601)\n  }\n}\n\nFUNNEL DETECTION:\nIf the user query mentions ANY of these concepts, use FUNNEL query format:\n- \"funnel\", \"conversion\", \"journey\", \"flow\"\n- \"step by step\", \"multi-step\", \"progression\"\n- \"drop off\", \"dropoff\", \"abandon\", \"churn\"\n- \"sign up to purchase\", \"registration to conversion\"\n- \"how many users go from X to Y\"\n\nFUNNEL QUERY RULES:\n1. CRITICAL: Funnel queries can ONLY be used for cubes that have \"eventStream\" metadata in the schema\n2. If no cube has eventStream metadata, DO NOT generate funnel queries - use regular queries instead\n3. Use \"funnel\" chart type when generating funnel queries\n4. bindingKey should match the eventStream.bindingKey from the cube metadata\n5. timeDimension should match the eventStream.timeDimension from the cube metadata\n6. Each step needs a name and filter that identifies that event\n7. Steps are ordered - step 2 must occur after step 1\n8. timeToConvert is optional but useful (e.g., \"P7D\" = 7 days, \"PT24H\" = 24 hours)\n9. ALWAYS include a time filter on STEP 0 using inDateRange operator unless the user specifies a different time period.\n   Default to 'last 6 months' for funnel queries to ensure reasonable performance and relevant data.\n   Add this as an additional filter in the first step's filter array.\n   Example: step 0 filter should include: { \"member\": \"PREvents.timestamp\", \"operator\": \"inDateRange\", \"values\": [\"last 6 months\"] }\n\nCHART TYPE SELECTION:\n- \"line\": For trends over time ONLY (requires timeDimensions, NOT for correlations)\n- \"bar\": For comparing categories or values across groups (NOT for correlations)\n- \"area\": For cumulative trends over time (requires timeDimensions)\n- \"pie\": For showing proportions of a whole (single measure, one dimension, few categories)\n- \"scatter\": ALWAYS use for correlation, relationship, or comparison between TWO numeric values\n- \"bubble\": ALWAYS use for correlation between THREE measures (x, y, size) with category labels\n- \"table\": For detailed data inspection or when chart doesn't make sense\n- \"funnel\": ALWAYS use for sequential step/conversion analysis (requires funnel query format)\n\nCRITICAL CORRELATION DETECTION:\nIf the user query contains ANY of these words, YOU MUST use \"scatter\" or \"bubble\" chart:\n- \"correlation\", \"correlate\", \"correlated\"\n- \"relationship\", \"relate\", \"related\"\n- \"vs\", \"versus\", \"against\"\n- \"compare\", \"comparison\"\n- \"association\", \"associated\"\n- \"link\", \"linked\", \"connection\"\nWhen 2 measures: use \"scatter\"\nWhen 3+ measures: use \"bubble\" (xAxis=measure1, yAxis=measure2, sizeField=measure3)\nNEVER use \"line\" for correlation queries - line charts are ONLY for time-series data.\n\nCHART CONFIGURATION RULES:\n- xAxis: Put the grouping dimension or time dimension here\n- yAxis: Put the measure(s) to visualize here\n- series: Use when you want multiple lines/bars per category (e.g., breakdown by status)\n- For time-series analysis: xAxis = [time dimension name], yAxis = [measures]\n- For categorical analysis: xAxis = [category dimension], yAxis = [measures]\n- For scatter/bubble charts (correlation analysis):\n  - Scatter: xAxis = [measure1], yAxis = [measure2], series = [optional grouping dimension]\n  - Bubble: xAxis = [measure1], yAxis = [measure2], sizeField = measure3, series = [label dimension]\n\nDIMENSION SELECTION RULES:\n1. ALWAYS prefer .name fields over .id fields (e.g., use \"Employees.name\" NOT \"Employees.id\")\n2. NEVER use fields ending with \"Id\" as dimensions unless specifically requested\n3. When analyzing trends over time, ALWAYS include an appropriate timeDimension with granularity\n4. For \"by\" queries (e.g., \"sales by region\"), use the category as the xAxis dimension\n5. Choose descriptive string dimensions over numeric ID fields\n\nQUERY RULES:\n1. Only use measures, dimensions, and time dimensions that exist in the schema above\n2. Return ONLY valid JSON - no explanations or markdown\n3. Use proper Cube.js query format with measures, dimensions, timeDimensions, filters, etc.\n4. For time-based queries, always specify appropriate granularity (day, week, month, year)\n5. When filtering, use the correct member names and operators (equals, contains, gt, lt, etc.)\n6. At least one measure or dimension is required\n\nUSER QUERY:\n{USER_PROMPT}\n\nReturn the JSON response:";
 /**
  * Build the single-step system prompt with schema and user prompt
  *

package/dist/client/charts.js

@@ -1,14 +1,14 @@
-import { dt as e, ft as t, gt as n, ht as r, lt as i, mt as a, pt as o, t as s, ut as c } from "./chunks/chart-data-table-BH1A-1RN.js";
-import { d as l, l as u, s as d, u as f } from "./chunks/chart-activity-grid-CSIsJ12e.js";
-import { t as p } from "./chunks/chart-funnel-C_-K4RLj.js";
-import { a as m, i as h, n as g, o as _, r as v, s as y, t as b } from "./chunks/charts-loader-BlxEsp39.js";
-import { t as x } from "./chunks/chart-area-BpvSKH5I.js";
+import { dt as e, ft as t, gt as n, ht as r, lt as i, mt as a, pt as o, t as s, ut as c } from "./chunks/chart-data-table-BdMo3zVh.js";
+import { d as l, l as u, s as d, u as f } from "./chunks/chart-activity-grid-DGazwi4C.js";
+import { t as p } from "./chunks/chart-funnel-BRyZS6ie.js";
+import { a as m, i as h, n as g, o as _, r as v, s as y, t as b } from "./chunks/charts-loader-BTI0UPK4.js";
+import { t as x } from "./chunks/chart-area-zyLGD-ym.js";
 import { i as S } from "./chunks/utils-CToHkuhU.js";
-import { t as C } from "./chunks/chart-bar-Cjzv-LvG.js";
-import { t as w } from "./chunks/chart-line-DlhmQQ-X.js";
-import { t as T } from "./chunks/chart-pie-CmKhmUR-.js";
-import { t as E } from "./chunks/chart-scatter-JnoA3CD5.js";
-import { t as D } from "./chunks/chart-radar-B2bYTyb0.js";
-import { t as O } from "./chunks/chart-radial-bar-DvQ-xZS-.js";
-import { t as k } from "./chunks/chart-tree-map-HQitd39D.js";
+import { t as C } from "./chunks/chart-bar-DMCBq8qJ.js";
+import { t as w } from "./chunks/chart-line-IEgiF8Nv.js";
+import { t as T } from "./chunks/chart-pie-BEB2sCXF.js";
+import { t as E } from "./chunks/chart-scatter-CSWF6-lx.js";
+import { t as D } from "./chunks/chart-radar-BbSbXKbP.js";
+import { t as O } from "./chunks/chart-radial-bar-CNYD7tkM.js";
+import { t as k } from "./chunks/chart-tree-map-BiXB7EiM.js";
 export { d as CHART_COLORS, u as CHART_MARGINS, s as DataTable, p as FunnelChart, b as LazyChart, f as NEGATIVE_COLOR, l as POSITIVE_COLOR, x as RechartsAreaChart, C as RechartsBarChart, w as RechartsLineChart, T as RechartsPieChart, D as RechartsRadarChart, O as RechartsRadialBarChart, E as RechartsScatterChart, k as RechartsTreeMapChart, i as clearChartConfigCache, S as formatChartData, g as getAvailableChartTypes, c as getChartConfigAsync, e as getChartConfigSync, v as getUnavailableChartTypes, t as isChartConfigLoaded, h as isChartTypeAvailable, m as isValidChartType, o as loadAllChartConfigs, _ as preloadChart, a as preloadChartConfig, r as preloadChartConfigs, y as preloadCharts, n as useChartConfig };

package/dist/client/chunks/{DashboardEditModal-USQFytJw.js → DashboardEditModal-DfaeSZGf.js}

@@ -1,16 +1,16 @@
-import { a as e, c as t, n, o as r, r as i, s as a, u as o } from "./vendor-C4pD7rZf.js";
+import { a as e, c as t, n, o as r, r as i, s as a, u as o } from "./vendor-DeckzF1j.js";
 import { n as s, t as c } from "./providers-DwQCKdGW.js";
-import { A as l, C as u, F as d, I as f, M as p, P as m, _t as h, ct as g, gt as _, j as v, v as y, y as b } from "./chart-data-table-BH1A-1RN.js";
-import { r as x } from "./chart-sankey-DHIrjmhj.js";
+import { A as l, C as u, F as d, I as f, M as p, P as m, _t as h, ct as g, gt as _, j as v, v as y, y as b } from "./chart-data-table-BdMo3zVh.js";
+import { r as x } from "./chart-sankey-DKnTIvSr.js";
 import { a as S, l as C, s as w } from "./retention-ChW9jYdy.js";
-import { i as T, t as E } from "./chart-markdown-C5ldCjSN.js";
+import { i as T, t as E } from "./chart-markdown-B_2Ed7FJ.js";
 import { c as D, f as O, n as k, o as A, p as j, r as M, t as N } from "./dashboardExport-Db3rmUP1.js";
-import { A as P, D as F, E as ee, L as I, S as te, T as L, a as R, d as ne, i as re, l as ie, n as ae, r as oe, s as z, t as se, u as ce, w as le, x as ue } from "./useDirtyStateTracking-DY5sjvb6.js";
-import { B as de, F as B, R as V } from "./chart-activity-grid-CSIsJ12e.js";
-import { a as fe, t as pe } from "./charts-loader-BlxEsp39.js";
-import { H as me } from "./chart-area-BpvSKH5I.js";
-import { n as he, t as ge } from "./charts-core-CQFOTTPb.js";
-import { n as H } from "./chart-gauge-F-vdq2BX.js";
+import { A as P, D as F, E as ee, L as I, S as te, T as L, a as R, d as ne, i as re, l as ie, n as ae, r as oe, s as z, t as se, u as ce, w as le, x as ue } from "./useDirtyStateTracking-BfG1lX_3.js";
+import { B as de, F as B, R as V } from "./chart-activity-grid-DGazwi4C.js";
+import { a as fe, t as pe } from "./charts-loader-BTI0UPK4.js";
+import { H as me } from "./chart-area-zyLGD-ym.js";
+import { n as he, t as ge } from "./charts-core-CKpkoMCa.js";
+import { n as H } from "./chart-gauge-DxgHlZKp.js";
 import _e, { Component as ve, Fragment as ye, Suspense as be, createContext as xe, forwardRef as Se, lazy as U, memo as W, startTransition as Ce, useCallback as G, useContext as we, useEffect as K, useImperativeHandle as Te, useMemo as q, useRef as J, useState as Y } from "react";
 import { Fragment as X, jsx as Z, jsxs as Q } from "react/jsx-runtime";
 import { createPortal as Ee } from "react-dom";
@@ -10271,7 +10271,7 @@ var ss = ({ isOpen: e, onClose: t, title: n, size: r = "md", closeOnBackdropClic
 			]
 		})
 	}) : null;
-}, cs = U(() => import("./analysis-builder-D_tw9BvU.js")), ls = Se((e, t) => /* @__PURE__ */ Z(be, {
+}, cs = U(() => import("./analysis-builder-fPK8NgJW.js")), ls = Se((e, t) => /* @__PURE__ */ Z(be, {
 	fallback: /* @__PURE__ */ Z("div", {
 		className: "dc:flex dc:items-center dc:justify-center dc:w-full dc:py-6",
 		children: /* @__PURE__ */ Z(me, {})
@@ -12623,4 +12623,4 @@ function Mc({ isOpen: e, onClose: t, onSave: n, title: r, submitText: i, initial
 //#endregion
 export { Ut as $, Kr as A, Tn as B, Vi as C, ci as D, Si as E, gn as F, xn as G, Dn as H, fn as I, _n as J, wn as K, An as L, Bn as M, Mn as N, oi as O, jn as P, Jt as Q, Cn as R, $i as S, Bi as T, Sn as U, bn as V, En as W, yn as X, vn as Y, cn as Z, Da as _, Oc as a, ke as at, Ui as b, pc as c, _s as d, Pt as et, ps as f, Zo as g, os as h, kc as i, Pe as it, Vn as j, $r as k, Ts as l, ss as m, jc as n, ze as nt, wc as o, Ae as ot, ls as p, kn as q, Ac as r, je as rt, gc as s, Mc as t, gt as tt, xs as u, ga as v, Hi as w, Wi as x, ha as y, On as z };
 
-//# sourceMappingURL=DashboardEditModal-USQFytJw.js.map
+//# sourceMappingURL=DashboardEditModal-DfaeSZGf.js.map