@luzmo/analytics-components-kit 1.0.1-alpha.136 → 1.0.1-alpha.138

package/components/item-context-configs.js

@@ -17,7 +17,7 @@
  * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
  * SOFTWARE.
  * */
-const defaultMeasureDescription = "The column used as measure in the chart. If an aggregation is asked like average, min, max, sum, count, distinctcount, median or weightedaverage, the aggregationType needs to be applied to the measure.", areaChartContextConfig = {
+var e$22 = "The column used as measure in the chart. If an aggregation is asked like average, min, max, sum, count, distinctcount, median or weightedaverage, the aggregationType needs to be applied to the measure.", a$6 = "The column used as category in the chart. A level is always required when using a datetime column. Else do not set a level.", t = {
 	name: "area-chart",
 	label: "Area Chart",
 	synonyms: [
@@ -30,13 +30,43 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		width: 580,
 		height: 250
 	},
+	variants: [
+		{
+			subtype: "area",
+			defaultSize: {
+				width: 580,
+				height: 250
+			}
+		},
+		{
+			subtype: "area-stack",
+			defaultSize: {
+				width: 580,
+				height: 250
+			}
+		},
+		{
+			subtype: "area-100",
+			defaultSize: {
+				width: 580,
+				height: 250
+			}
+		},
+		{
+			subtype: "area-stream",
+			defaultSize: {
+				width: 580,
+				height: 300
+			}
+		}
+	],
 	description: "Creates an area chart. An area chart can consist of multiple lines by using a legend.\n    Each line or area represents a category. Legends are mostly columns with a type of hierarchy.\n    Most of the time columns with type datetime are used for the x-axis of an area chart. Sometimes also columns with numeric types can be used.\n    Often columns with type numeric are used as measure. If you want to display area over a second dimension, use a legend.\n    First fill in an x-axis and measure, ONLY when using another column or dimension, use a legend.\n    You can not have multiple measures together with a legend, it is one or the other.\n    To have multiple measures in an area chart use more than one column/formula in measures, to report a measure across two dimensions use a legend.",
 	slots: {
-		measure: { description: defaultMeasureDescription },
+		measure: { description: e$22 },
 		"x-axis": { description: "The column used as x-axis in the chart.\n        This slot is required and determines the horizontal positioning of data points." },
-		legend: { description: "The column used as legend in the chart. Only add a legend if it is relevant to the chart. \n        A legend is used to show a second dimension in the chart and allows grouping of data series. A legend cannot coexist with multiple measures" }
+		legend: { description: "The column used as legend in the chart. Only add a legend if it is relevant to the chart.\n        A legend is used to show a second dimension in the chart and allows grouping of data series. A legend cannot coexist with multiple measures" }
 	}
-}, barChartContextConfig = {
+}, t$1 = {
 	name: "bar-chart",
 	label: "Bar Chart",
 	synonyms: [
@@ -51,11 +81,11 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	},
 	description: "Creates a bar chart. A bar chart can consist of multiple bars. Each bar represents a category.\n    A category is mostly a column with a type of hierarchy or datetime. Often columns with type numeric are used as measure.\n    First fill in a category and measure, ONLY when using a another column or dimension, use a legend.\n    You can not have multiple measures together with a legend, it is one or the other.\n    To have multiple measures in a bar chart use more than one column/formula in measures, to report a measure across two dimensions use a legend.",
 	slots: {
-		measure: { description: defaultMeasureDescription },
+		measure: { description: e$22 },
 		"y-axis": { description: "The column used as y-axis in the chart. The y-axis in a bar chart is the category that is being used, not the measure.\n        Typical this is a column with a type of hierarchy or datetime and is NOT the same column that is used as a measure.\n        Numeric columns are not often used as y-axis in a bar chart unless a user asks them to be binned." },
 		legend: { description: "The column used as legend in the chart. Only add a legend if it is relevant to the chart. A legend is used to show a second dimension in the chart." }
 	}
-}, boxPlotContextConfig = {
+}, e = {
 	name: "box-plot",
 	label: "Box Plot",
 	synonyms: [
@@ -67,12 +97,12 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		width: 580,
 		height: 480
 	},
-	description: "Creates a box plot. A box plot displays the distribution of data through quartiles, showing the median, \n    interquartile range, and potential outliers. Box plots are effective for comparing distributions across categories\n    and identifying skewness or unusual data points. They work well with numeric data and categorical groupings.",
+	description: "Creates a box plot. A box plot displays the distribution of data through quartiles, showing the median,\n    interquartile range, and potential outliers. Box plots are effective for comparing distributions across categories\n    and identifying skewness or unusual data points. They work well with numeric data and categorical groupings.",
 	slots: {
 		measure: { description: "The column used as measure in the chart. This determines the numeric values to be analyzed.\n        Must be a numeric column type. The box plot will show the distribution of these values." },
 		category: { description: "The column used as category in the chart. This determines how the data is grouped for comparison.\n        Typically this is a column with a type of hierarchy or datetime. Each category will have its own box plot." }
 	}
-}, bubbleChartContextConfig = {
+}, e$1 = {
 	name: "bubble-chart",
 	label: "Bubble Chart",
 	synonyms: [
@@ -84,13 +114,13 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		width: 580,
 		height: 580
 	},
-	description: "Creates a bubble chart. A bubble chart can consist of multiple bubbles. Each bubble represents a category.\n    Categories are mostly columns with a type of hierarchy or datetime. The size of the bubble represents the measure. \n    Often columns with type numeric are used as measure. If you want to use a second dimension, use a legend (slot color).",
+	description: "Creates a bubble chart. A bubble chart can consist of multiple bubbles. Each bubble represents a category.\n    Categories are mostly columns with a type of hierarchy or datetime. The size of the bubble represents the measure.\n    Often columns with type numeric are used as measure. If you want to use a second dimension, use a legend (slot color).",
 	slots: {
 		category: { description: "The column used as category in the chart. This column is used to define what the bubbles are in the bubble chart. This slot is required." },
 		measure: { description: "The column used to determine the size of bubbles. Typically a numeric column or a count or distinct count of another type of column." },
 		color: { description: "The column used as legend in the chart. Only add a legend if it is relevant to the chart.\n        This column is used in case of a second dimension to color the bubbles." }
 	}
-}, bulletChartContextConfig = {
+}, a = {
 	name: "bullet-chart",
 	label: "Bullet Chart",
 	synonyms: [
@@ -104,11 +134,11 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	},
 	description: "Creates a bullet chart. A bullet chart displays a measure against a target value.\n    Bullet charts are effective for showing progress toward goals.\n    Use measure for the actual value, target for the goal, and optionally category for grouping.",
 	slots: {
-		measure: { description: defaultMeasureDescription },
+		measure: { description: e$22 },
 		target: { description: "The column used as target in the chart. This determines the goal or benchmark value to compare against.\n        Typically a numeric column. The target is displayed as a marker on the bullet chart." },
 		category: { description: "The column used as category in the chart. This determines how the bullet charts are grouped or labeled.\n        Typically this is a column with a type of hierarchy or datetime. Each category becomes a separate bullet chart." }
 	}
-}, choroplethMapContextConfig = {
+}, a$1 = {
 	name: "choropleth-map",
 	label: "Choropleth Map",
 	synonyms: ["choropleth", "choropleth map"],
@@ -119,10 +149,10 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	description: "Creates a choropleth map. A choropleth map displays geographic data by coloring regions based on their values.\n    Use geography for the spatial boundaries and measure for the values.\n    Optionally use category for grouping or additional dimensions.",
 	slots: {
 		geo: { description: "The column used for geography in the map. This determines the spatial boundaries and regions.\n        Is required and must be a spatial column type. This defines the geographic areas that will be colored on the map." },
-		measure: { description: defaultMeasureDescription },
+		measure: { description: e$22 },
 		category: { description: "The column used as category in the map. Typically this is a column with a type of hierarchy or datetime. This allows for additional analysis dimensions." }
 	}
-}, circlePackChartContextConfig = {
+}, a$2 = {
 	name: "circle-pack-chart",
 	label: "Circle Pack Chart",
 	synonyms: [
@@ -134,12 +164,12 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		width: 580,
 		height: 600
 	},
-	description: "Creates a circle pack chart. A circle pack diagram can consist of multiple levels. Each level represents a category. \n    A circle pack chart displays hierarchical data as nested circles, where the size of each circle\n    represents a value. They work well with hierarchical data and can display multiple levels of nesting.\n    The measure is the column that is represented over all levels.",
+	description: "Creates a circle pack chart. A circle pack diagram can consist of multiple levels. Each level represents a category.\n    A circle pack chart displays hierarchical data as nested circles, where the size of each circle\n    represents a value. They work well with hierarchical data and can display multiple levels of nesting.\n    The measure is the column that is represented over all levels.",
 	slots: {
-		measure: { description: defaultMeasureDescription },
+		measure: { description: e$22 },
 		levels: { description: "The column(s) used as levels in the chart. These determine the hierarchical structure of the data.\n        Multiple columns can be used to create multi-level hierarchies. Each level becomes a nested circle in the chart.\n        Typically these are columns with a type of hierarchy or datetime." }
 	}
-}, circularGaugeContextConfig = {
+}, e$2 = {
 	name: "circular-gauge",
 	label: "Circular Gauge",
 	synonyms: [
@@ -156,7 +186,7 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		measure: { description: "The column used as measure in the gauge. This determines the current value to be displayed." },
 		target: { description: "The column used as target in the gauge. This determines the goal or maximum value for the scale." }
 	}
-}, columnChartContextConfig = {
+}, a$3 = {
 	name: "column-chart",
 	label: "Column Chart",
 	synonyms: [
@@ -169,13 +199,36 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		width: 580,
 		height: 350
 	},
+	variants: [
+		{
+			subtype: "column",
+			defaultSize: {
+				width: 580,
+				height: 350
+			}
+		},
+		{
+			subtype: "column-group",
+			defaultSize: {
+				width: 580,
+				height: 350
+			}
+		},
+		{
+			subtype: "column-stack",
+			defaultSize: {
+				width: 580,
+				height: 350
+			}
+		}
+	],
 	description: "Creates a column chart. A column chart can consist of multiple columns. Each column represents a category.\n    A category is mostly a column with a type of hierarchy or datetime. Often columns with type numeric are used as measure.\n    First fill in a category and measure, ONLY when using a another column or dimension, use a legend.\n    You can not have multiple measures together with a legend, it is one or the other.\n    To have multiple measures in a column chart use more than one column/formula in measures, to report a measure across two dimensions use a legend.",
 	slots: {
-		measure: { description: defaultMeasureDescription },
+		measure: { description: e$22 },
 		"x-axis": { description: "The column used as x-axis in the chart. The x-axis in a column chart is the category that is being used, not the measure.\n        Typically this is a column with a type of hierarchy or datetime and is NOT the same column that is used as a measure.\n        Numeric columns are not often used as x-axis in a column chart unless a user asks them to be binned." },
-		legend: { description: "The column used as legend in the chart. Only add a legend if it is relevant to the chart. \n        A legend is used to show a second dimension in the chart." }
+		legend: { description: "The column used as legend in the chart. Only add a legend if it is relevant to the chart.\n        A legend is used to show a second dimension in the chart." }
 	}
-}, combinationChartContextConfig = {
+}, o = {
 	name: "combination-chart",
 	label: "Combination Chart",
 	synonyms: [
@@ -197,10 +250,10 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	},
 	description: "Creates a combination chart. A combination chart combines different chart types in a single visualization,\n    such as bars and lines, dots or areas. Combination charts are effective for comparing different types of data\n    or showing relationships between different metrics on the same scale.",
 	slots: {
-		measure: { description: defaultMeasureDescription },
+		measure: { description: e$22 },
 		"x-axis": { description: "The column used as x-axis in the chart. This determines the horizontal positioning of data points.\n        For time series data, use datetime columns. For categorical data, use hierarchy columns.\n        This slot is required and determines the horizontal positioning of data points." }
 	}
-}, conditionalNumberContextConfig = {
+}, e$3 = {
 	name: "conditional-number",
 	label: "Conditional Number",
 	synonyms: [
@@ -219,7 +272,7 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		measure: { description: "The column used as measure in the display. This determines the current value to be shown." },
 		target: { description: "The column used as target in the display. This determines the comparison value for conditional formatting." }
 	}
-}, dateComparisonFilterContextConfig = {
+}, e$4 = {
 	name: "date-comparison-filter",
 	label: "Date Comparison Filter",
 	synonyms: [
@@ -231,9 +284,9 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		width: 350,
 		height: 125
 	},
-	description: "Creates a date comparison filter. A date comparison filter allows users to set two date ranges to \n    filter dashboard data based on two date or time ranges. This enables users to compare data across different time periods",
+	description: "Creates a date comparison filter. A date comparison filter allows users to set two date ranges to\n    filter dashboard data based on two date or time ranges. This enables users to compare data across different time periods",
 	slots: { time: { description: "The column used for datetime filtering. This determines which datetime data that can be filtered on.\n        Must be a datetime column type." } }
-}, dateFilterContextConfig = {
+}, e$5 = {
 	name: "date-filter",
 	label: "Date Filter",
 	synonyms: [
@@ -247,7 +300,7 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	},
 	description: "Creates a date filter. A date filter allows users to filter dashboard data based on date or time ranges.\n    Date filters are effective for time-based analysis, allowing users to focus on specific time periods\n    or compare data across different date ranges.",
 	slots: { time: { description: "The column used for datetime filtering. This determines which datetime data that can be filtered on.\n        Must be a datetime column type." } }
-}, donutChartContextConfig = {
+}, a$4 = {
 	name: "donut-chart",
 	label: "Donut Chart",
 	synonyms: [
@@ -262,12 +315,42 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		width: 400,
 		height: 400
 	},
+	variants: [
+		{
+			subtype: "pie",
+			defaultSize: {
+				width: 400,
+				height: 400
+			}
+		},
+		{
+			subtype: "donut",
+			defaultSize: {
+				width: 400,
+				height: 400
+			}
+		},
+		{
+			subtype: "half-pie",
+			defaultSize: {
+				width: 400,
+				height: 400
+			}
+		},
+		{
+			subtype: "half-donut",
+			defaultSize: {
+				width: 400,
+				height: 400
+			}
+		}
+	],
 	description: "Creates a donut or a pie chart. A donut or pie chart consists of multiple slices. Each slice represents a category.\n    Categories are mostly columns with a type of hierarchy or datetime. The width of the slice represents the measure of the category.\n    Often columns with type numeric are used as measure.",
 	slots: {
-		measure: { description: defaultMeasureDescription },
-		category: { description: "The column used as category in the chart. A level is always required when using a datetime column. Else do not set a level." }
+		measure: { description: e$22 },
+		category: { description: a$6 }
 	}
-}, dropdownFilterContextConfig = {
+}, e$6 = {
 	name: "dropdown-filter",
 	label: "Dropdown Filter",
 	synonyms: [
@@ -284,7 +367,7 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	},
 	description: "Creates a dropdown filter. A dropdown filter allows users to filter dashboard data by selecting values from a dropdown list.\n    Dropdown filters are effective for categorical filtering, allowing users to focus on specific categories or values\n    from a dimension.",
 	slots: { dimension: { description: "The column used for dimension filtering. This determines the data that can be filtered.\n        Can be mixed data types including hierarchy, datetime, and numeric. This defines the dimension that users can filter on." } }
-}, evolutionNumberContextConfig = {
+}, t$2 = {
 	name: "evolution-number",
 	label: "Evolution Number",
 	synonyms: [
@@ -301,10 +384,10 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	},
 	description: "Creates a number display. An evolution number shows a single value with an optional evolution indicator.\n    Evolution numbers are effective for displaying key metrics with trend information, allowing users to see both current values\n    and how they have changed over time. They work well for KPIs and important metrics that need trend context.\n    Use measure for the main value and optionally evolution for the time dimension to show trends.",
 	slots: {
-		measure: { description: defaultMeasureDescription },
+		measure: { description: e$22 },
 		evolution: { description: "The column used to optionally show evolution of the number. This determines the time dimension for trend analysis.\n        Must be a datetime column type. This defines the time period over which the evolution is calculated." }
 	}
-}, funnelChartContextConfig = {
+}, e$7 = {
 	name: "funnel-chart",
 	label: "Funnel Chart",
 	synonyms: [
@@ -321,7 +404,7 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		measure: { description: "The column used as measure in the chart. This determines the values for each stage in the funnel.\n        Can be numeric or hierarchy columns. These values determine the size of each funnel section." },
 		category: { description: "The column used as category in the chart. This determines the stages or steps in the funnel.\n        Typically this is a column with a type of hierarchy or datetime. Each category becomes a section in the funnel." }
 	}
-}, heatMapContextConfig = {
+}, t$3 = {
 	name: "heat-map",
 	label: "Heat Map",
 	synonyms: ["heatmap", "heat map"],
@@ -332,9 +415,9 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	description: "Creates a heat map. A heat map displays data as a grid where each cell is colored based on its value.\n    Heat maps are effective for showing patterns in large datasets and identifying correlations between variables.\n    They work well with geographic data, correlation matrices, and any data that can be organized in a grid format.\n    Use geography for spatial data and measures for the values to be visualized.",
 	slots: {
 		geo: { description: "The column used for geography in the heat map. This determines the spatial layout of the data.\n        Must be a spatial column type. This slot is required for geographic heat maps." },
-		measure: { description: defaultMeasureDescription }
+		measure: { description: e$22 }
 	}
-}, heatTableContextConfig = {
+}, t$4 = {
 	name: "heat-table",
 	label: "Heat Table",
 	synonyms: [
@@ -350,9 +433,9 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	slots: {
 		"x-axis": { description: "The column used as x-axis in the table. This determines the columns in the heat table.\n        Can be categorical data types including hierarchy and datetime. Each unique value becomes a column in the table." },
 		"y-axis": { description: "The column used as y-axis in the table. This determines the rows in the heat table.\n        Can be categorical data types including hierarchy and datetime. Each unique value becomes a row in the table." },
-		measure: { description: defaultMeasureDescription }
+		measure: { description: e$22 }
 	}
-}, hexbinMapContextConfig = {
+}, i = {
 	name: "hexbin-map",
 	label: "Hexbin Map",
 	synonyms: ["hexbin", "hexbin map"],
@@ -363,9 +446,9 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	description: "Creates a hexbin map. A hexbin map displays geographic data by aggregating points into hexagonal bins on a map.\n    Hexbin maps are effective for showing density patterns, clustering of geographic data points, and spatial distributions\n    with many overlapping points. They work well with spatial coordinates and numeric values, especially for large datasets.\n    Use geography for the spatial coordinates and measure for the values to be aggregated within each hexbin.",
 	slots: {
 		geo: { description: "The column used for geography in the map. This determines the spatial coordinates for hexbin placement.\n        Must be a spatial column type. This defines the geographic locations that will be aggregated into hexagonal bins." },
-		measure: { description: defaultMeasureDescription }
+		measure: { description: e$22 }
 	}
-}, imageContextConfig = {
+}, e$8 = {
 	name: "image",
 	label: "Image",
 	synonyms: ["image", "image element"],
@@ -375,7 +458,7 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	},
 	description: "Creates an image element. An image element displays static images on a dashboard.\n    Image elements are effective for adding logos, icons, diagrams, or any visual content to dashboards.\n    They work well for branding, visual explanations, or decorative purposes.\n    Image elements can be configured with various sizing and positioning options.",
 	slots: {}
-}, lineChartContextConfig = {
+}, t$5 = {
 	name: "line-chart",
 	label: "Line Chart",
 	synonyms: [
@@ -389,13 +472,26 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		width: 580,
 		height: 250
 	},
+	variants: [{
+		subtype: "line",
+		defaultSize: {
+			width: 580,
+			height: 250
+		}
+	}, {
+		subtype: "line-group",
+		defaultSize: {
+			width: 580,
+			height: 250
+		}
+	}],
 	description: "Creates a line chart. A line chart displays data as a series of points connected by straight lines.\n    Line charts are ideal for showing trends over time and continuous data. They work well with time series data\n    and can display multiple series for comparison. Use measures for the values and x-axis for categories or time periods.\n    Legends can be used to group data by additional dimensions.",
 	slots: {
-		measure: { description: defaultMeasureDescription },
+		measure: { description: e$22 },
 		"x-axis": { description: "The column used as x-axis in the chart. This is typically a category or time dimension.\n        For time series data, use datetime columns. For categorical data, use hierarchy columns.\n        This slot is required and determines the horizontal positioning of data points." },
-		legend: { description: "The column used as legend in the chart. Only add a legend if it is relevant to the chart. \n        A legend is used to show a second dimension in the chart and allows grouping of data series." }
+		legend: { description: "The column used as legend in the chart. Only add a legend if it is relevant to the chart.\n        A legend is used to show a second dimension in the chart and allows grouping of data series." }
 	}
-}, markerMapContextConfig = {
+}, r = {
 	name: "marker-map",
 	label: "Marker Map",
 	synonyms: [
@@ -411,9 +507,9 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	description: "Creates a marker map. A marker map displays geographic data using markers or pins at specific locations.\n    Marker maps are effective for showing point-based geographic data, locations of interest, or discrete geographic events.\n    They work well with spatial coordinates and can represent different types of locations or events.\n    Use geography for the spatial coordinates and measure for the values to be displayed.",
 	slots: {
 		geo: { description: "The column used for geography in the map. This determines the spatial coordinates for marker placement.\n        Must be a spatial column type. This defines the geographic locations where markers will be displayed." },
-		measure: { description: defaultMeasureDescription }
+		measure: { description: e$22 }
 	}
-}, ohlcChartContextConfig = {
+}, e$9 = {
 	name: "ohlc-chart",
 	label: "OHLC Chart",
 	synonyms: [
@@ -427,6 +523,19 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		width: 580,
 		height: 400
 	},
+	variants: [{
+		subtype: "ohlc",
+		defaultSize: {
+			width: 580,
+			height: 400
+		}
+	}, {
+		subtype: "candlestick",
+		defaultSize: {
+			width: 580,
+			height: 400
+		}
+	}],
 	description: "Creates an OHLC (Open-High-Low-Close) chart. An OHLC chart displays financial data showing the opening, high, low, and closing prices.\n    OHLC charts are effective for analyzing financial markets, stock prices, and other time-series financial data.\n    They work well for identifying trends, patterns, and volatility in financial instruments.\n    Use open, high, low, and close for the price data and x-axis for the time dimension.",
 	slots: {
 		open: { description: "The column used for opening prices. This determines the opening value for each time period.\n        Must be a numeric column type. This represents the price at the beginning of each time period." },
@@ -435,7 +544,7 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		close: { description: "The column used for closing prices. This determines the closing value for each time period.\n        Must be a numeric column type. This represents the price at the end of each time period." },
 		"x-axis": { description: "The column used as x-axis in the chart. This determines the time dimension for the OHLC data.\n        Must be a datetime column type. This defines the time periods for which the OHLC values are calculated." }
 	}
-}, parallelCoordinatesPlotContextConfig = {
+}, e$10 = {
 	name: "parallel-coordinates-plot",
 	label: "Parallel Coordinates Plot",
 	synonyms: [
@@ -452,7 +561,7 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		coordinates: { description: "The column(s) used as coordinates in the plot. These determine the variables represented by each axis.\n        Multiple columns can be used to create multiple axes. Each coordinate becomes a vertical axis in the plot.\n        Can be mixed data types including numeric, datetime, and categorical." },
 		color: { description: "The column used to determine the color of data lines. Typically a categorical column.\n        Different categories are represented by different colors, allowing identification of patterns across groups." }
 	}
-}, pivotTableContextConfig = {
+}, a$5 = {
 	name: "pivot-table",
 	label: "Pivot Table",
 	synonyms: [
@@ -469,9 +578,9 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	slots: {
 		row: { description: "The column(s) used as rows in the pivot table. These determine the vertical grouping of data.\n        Typically these are categorical columns (hierarchy or datetime). Multiple columns can be used to create hierarchical rows." },
 		column: { description: "The column(s) used as columns in the pivot table. These determine the horizontal grouping of data.\n        Typically these are categorical columns (hierarchy or datetime). Multiple columns can be used to create hierarchical columns." },
-		measure: { description: defaultMeasureDescription }
+		measure: { description: e$22 }
 	}
-}, pyramidChartContextConfig = {
+}, i$1 = {
 	name: "pyramid-chart",
 	label: "Pyramid Chart",
 	synonyms: [
@@ -486,10 +595,10 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	description: "Creates a pyramid chart. A pyramid chart displays data as horizontal bars arranged in a pyramid shape,\n    typically used for population demographics or hierarchical data. Pyramid charts are effective for showing\n    the distribution of data across categories and comparing values between different groups.\n    Use measure for the values, y-axis for categories, and optionally legend for grouping.",
 	slots: {
 		"y-axis": { description: "The column used as y-axis in the chart. This determines the categories or bins displayed in the pyramid.\n        Typically this is a column with a type of hierarchy or datetime. Each category becomes a horizontal bar in the pyramid." },
-		measure: { description: defaultMeasureDescription },
+		measure: { description: e$22 },
 		legend: { description: "The column used as legend in the chart. Only add a legend if it is relevant to the chart.\n        A legend is used to show a second dimension in the chart and allows grouping of data series." }
 	}
-}, radarChartContextConfig = {
+}, e$11 = {
 	name: "radar-chart",
 	label: "Radar Chart",
 	synonyms: [
@@ -507,7 +616,7 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		category: { description: "The column used as category in the chart. This determines the variables represented by each axis.\n        Typically this is a column with a type of hierarchy or datetime. Each category becomes an axis in the radar chart." },
 		color: { description: "The column used to determine the color of data series. Typically a categorical column.\n        Different categories are represented by different colors, allowing comparison of multiple series." }
 	}
-}, regularTableContextConfig = {
+}, e$12 = {
 	name: "regular-table",
 	label: "Regular Table",
 	synonyms: [
@@ -521,7 +630,7 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	},
 	description: "Creates a regular table. A regular table displays data in a structured format with rows and columns.\n    Regular tables are effective for displaying detailed data, allowing users to see individual records and values.\n    They work well for data exploration, detailed analysis, and when users need to see specific values.\n    Use columns to specify which data fields to display in the table.",
 	slots: { columns: { description: "The column(s) used as columns in the table. These determine which data fields are displayed.\n        Can be mixed data types including numeric, datetime, hierarchy, and text. Multiple columns can be selected\n        to create a comprehensive table view." } }
-}, routeMapContextConfig = {
+}, e$13 = {
 	name: "route-map",
 	label: "Route Map",
 	synonyms: [
@@ -540,7 +649,7 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		route: { description: "The column used for route grouping. This determines how coordinates are grouped into different routes.\n        Can be mixed data types. Different values create separate route lines on the map." },
 		legend: { description: "The column used as legend in the map. This determines the color coding for different routes or segments.\n        Can be mixed data types. Different values are represented by different colors on the route lines." }
 	}
-}, sankeyDiagramContextConfig = {
+}, t$6 = {
 	name: "sankey-diagram",
 	label: "Sankey Diagram",
 	synonyms: [
@@ -556,14 +665,27 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		width: 580,
 		height: 500
 	},
+	variants: [{
+		subtype: "sankey",
+		defaultSize: {
+			width: 580,
+			height: 500
+		}
+	}, {
+		subtype: "alluvial",
+		defaultSize: {
+			width: 580,
+			height: 500
+		}
+	}],
 	description: "Creates a Sankey diagram. A Sankey diagram displays the flow of data between different nodes or categories,\n    where the width of the flow represents the quantity. Sankey diagrams are effective for showing the movement of resources,\n    energy, or data through a system. The sankey diagram has two modes: a sankey mode and a alluvial mode:\n      - Sankey mode: This is the default mode. It is used to show the flow of data fro source to destination.\n      - Alluvial mode: This is used to show the flow of data between categories. It doesn't use source and destination, but instead uses multiple categories.",
 	slots: {
 		source: { description: "Only use this in sankey mode.The column used as source in the diagram. This determines the starting point of each flow.\n        Typically this is a column with a type of hierarchy or datetime. Each unique value becomes a source node." },
 		destination: { description: "Only use this in sankey mode.The column used as destination in the diagram. This determines the ending point of each flow.\n        Typically this is a column with a type of hierarchy or datetime. Each unique value becomes a destination node." },
-		measure: { description: defaultMeasureDescription },
+		measure: { description: e$22 },
 		category: { description: "Only use this in alluvial mode.The columns used as categories in the diagram.\n      In an alluvial diagram, the categories are used to group the flows." }
 	}
-}, scatterPlotContextConfig = {
+}, e$14 = {
 	name: "scatter-plot",
 	label: "Scatter Plot",
 	synonyms: [
@@ -576,6 +698,36 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		width: 580,
 		height: 300
 	},
+	variants: [
+		{
+			subtype: "scatter",
+			defaultSize: {
+				width: 580,
+				height: 300
+			}
+		},
+		{
+			subtype: "scatter-group",
+			defaultSize: {
+				width: 580,
+				height: 300
+			}
+		},
+		{
+			subtype: "bubble",
+			defaultSize: {
+				width: 580,
+				height: 300
+			}
+		},
+		{
+			subtype: "bubble-group",
+			defaultSize: {
+				width: 580,
+				height: 300
+			}
+		}
+	],
 	description: "Creates a scatter plot. A scatter plot displays data points on a two-dimensional coordinate system.\n    Scatter plots are used to show the relationship between two variables and identify patterns, correlations, or outliers.\n    Each point represents an observation with values for both x and y axes. Size and color can be used to encode additional dimensions.\n    Use x-axis and y-axis for the main variables, and optionally size and color for additional dimensions.",
 	slots: {
 		"x-axis": { description: "The column used as x-axis in the chart. This determines the horizontal position of each data point. This slot is required." },
@@ -584,7 +736,7 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		color: { description: "The column used to determine the color of data points. Typically a categorical column.\n        Different categories are represented by different colors, allowing visualization of a fourth dimension." },
 		name: { description: "The column used to label data points. Can be used for tooltips or point identification.\n        Multiple columns can be used to create composite labels." }
 	}
-}, searchFilterContextConfig = {
+}, e$15 = {
 	name: "search-filter",
 	label: "Search Filter",
 	synonyms: [
@@ -599,7 +751,7 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	},
 	description: "Creates a selectbox with search and a dropdown menu. A search filter allows users to filter dashboard data by typing search terms.\n    Selectboxes or search filters are effective for categorical filtering, allowing users to quickly find specific values\n    within a dimension. They work well with hierarchical data and provide fast, flexible filtering capabilities.\n    Use dimension for the categorical column to be searched.",
 	slots: { dimension: { description: "The column used for dimension searching. This determines the data that can be searched.\n        Must be a hierarchy column type. This defines the dimension that users can search within." } }
-}, slicerFilterContextConfig = {
+}, e$16 = {
 	name: "slicer-filter",
 	label: "Slicer Filter",
 	synonyms: [
@@ -615,12 +767,42 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		width: 300,
 		height: 300
 	},
+	variants: [
+		{
+			subtype: "vertical",
+			defaultSize: {
+				width: 300,
+				height: 300
+			}
+		},
+		{
+			subtype: "horizontal",
+			defaultSize: {
+				width: 600,
+				height: 100
+			}
+		},
+		{
+			subtype: "table",
+			defaultSize: {
+				width: 400,
+				height: 380
+			}
+		},
+		{
+			subtype: "rank-vertical",
+			defaultSize: {
+				width: 300,
+				height: 300
+			}
+		}
+	],
 	description: "Creates a slicer filter. A slicer filter allows users to filter dashboard data by selecting values from a visual list.\n    Slicer filters are effective for categorical filtering with visual representation, allowing users to see all available options\n    and select multiple values. They work well with any data type and provide an intuitive filtering interface.\n    Use dimension for the column to be filtered and optionally measure for additional context.",
 	slots: {
 		dimension: { description: "The column used for dimension filtering. This determines the data that can be filtered.\n        Can be mixed data types including hierarchy, datetime, and numeric. This defines the dimension that users can filter on." },
 		measure: { description: "The column used as measure in the filter. This provides additional context for the filter options.\n        Typically a numeric column. This can show counts or other metrics for each filter option." }
 	}
-}, sliderFilterContextConfig = {
+}, e$17 = {
 	name: "slider-filter",
 	label: "Slider Filter",
 	synonyms: [
@@ -636,7 +818,7 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	},
 	description: "Creates a slider filter. A slider filter allows users to filter dashboard data by selecting a range of values using a slider.\n  Slider filters are effective for range-based filtering, allowing users to select minimum and maximum values\n  for numeric or datetime data. They work well with continuous data and provide intuitive range selection.\n  Use slidermetric for the numeric or datetime column to be filtered.",
 	slots: { slidermetric: { description: "The column used for slider filtering.This must be a column with a type of numeric or of datetime.\n      Only a numeric or datetime columns can be used for filtering." } }
-}, speedometerChartContextConfig = {
+}, e$18 = {
 	name: "speedometer-chart",
 	label: "Speedometer Chart",
 	synonyms: [
@@ -655,7 +837,7 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		measure: { description: "The column used as measure in the chart. This determines the current value to be displayed.\n        Must be a numeric column. This value is displayed as the position on the speedometer gauge." },
 		target: { description: "The column used as target in the chart. This determines the goal or maximum value for the scale.\n        Typically a numeric column. The target helps define the scale and context for the measure value." }
 	}
-}, spikeMapContextConfig = {
+}, s = {
 	name: "spike-map",
 	label: "Spike Map",
 	synonyms: ["spike", "spike map"],
@@ -666,10 +848,10 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	description: "Creates a spike map. A spike map displays geographic data using vertical spikes or bars at specific locations.\n    Spike maps are effective for showing geographic data with varying magnitudes, such as population density, sales volume,\n    or any metric that varies by location. They work well with spatial coordinates and numeric values.\n    Use geography for the spatial coordinates, measure for the values, and optionally color for additional dimensions.",
 	slots: {
 		geo: { description: "The column used for geography in the map. This determines the spatial coordinates for spike placement.\n        Must be a spatial column type. This defines the geographic locations where spikes will be displayed." },
-		measure: { description: defaultMeasureDescription },
+		measure: { description: e$22 },
 		color: { description: "The column used to determine the color of spikes. This can be used to encode additional dimensions.\n        Can be mixed data types. Different values are represented by different colors on the spikes." }
 	}
-}, stripPlotContextConfig = {
+}, e$19 = {
 	name: "strip-plot",
 	label: "Strip Plot",
 	synonyms: [
@@ -683,10 +865,10 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	},
 	description: "Creates a strip plot. A strip plot displays individual data points along a single axis, grouped by categories.\n    Strip plots are effective for showing the distribution of data within categories and identifying patterns or outliers.\n    They work well with small to medium datasets and are useful for comparing distributions across different groups.\n    Use measure for the numeric values and y-axis for the categories.",
 	slots: {
-		measure: { description: defaultMeasureDescription },
+		measure: { description: e$22 },
 		"y-axis": { description: "The column used as y-axis in the chart. This determines the categories for grouping the data points.\n        Typically this is a column with a type of hierarchy or datetime. Each category becomes a group of data points." }
 	}
-}, sunburstChartContextConfig = {
+}, r$1 = {
 	name: "sunburst-chart",
 	label: "Sunburst Chart",
 	synonyms: [
@@ -700,10 +882,10 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	},
 	description: "Creates a sunburst chart. A sunburst chart displays hierarchical data as concentric rings, where each ring represents a level\n    in the hierarchy. Sunburst charts are effective for showing the composition of hierarchical data and identifying patterns\n    at different levels. They work well with multi-level hierarchies and can display large amounts of data in a compact space.\n    Use measure for the values and levels for the hierarchical structure.",
 	slots: {
-		measure: { description: defaultMeasureDescription },
+		measure: { description: e$22 },
 		levels: { description: "The column(s) used as levels in the chart. These determine the hierarchical structure of the data.\n        Multiple columns can be used to create multi-level hierarchies. Each level becomes a ring in the sunburst chart.\n        Typically these are columns with a type of hierarchy or datetime." }
 	}
-}, symbolMapContextConfig = {
+}, s$1 = {
 	name: "symbol-map",
 	label: "Symbol Map",
 	synonyms: [
@@ -718,10 +900,10 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	description: "Creates a symbol map. A symbol map displays geographic data using symbols or icons at specific locations.\n    Symbol maps are effective for showing point-based geographic data, locations of interest, or discrete geographic events.\n    They work well with spatial coordinates and can represent different types of locations or events using various symbols.\n    Use geography for the spatial coordinates, measure for the values, and optionally category for grouping or color coding.",
 	slots: {
 		geo: { description: "The column used for geography in the map. This determines the spatial coordinates for symbol placement.\n        Must be a spatial column type. This defines the geographic locations where symbols will be displayed." },
-		measure: { description: defaultMeasureDescription },
+		measure: { description: e$22 },
 		category: { description: "The column used as category in the map. This determines the grouping or color coding for different symbols.\n        Can be hierarchy, datetime, or array types. Different categories can be represented by different symbols or colors." }
 	}
-}, textContextConfig = {
+}, t$7 = {
 	name: "text",
 	label: "Text",
 	synonyms: [
@@ -735,7 +917,7 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	},
 	description: "Creates a text element. A text element displays static or dynamic text content on a dashboard.\n    Text elements are effective for adding titles, descriptions, labels, or any textual information to dashboards.\n    They work well for providing context, instructions, or explanations for other dashboard elements.\n    Text elements can be configured with various formatting options and can include dynamic content.",
 	slots: {}
-}, treemapChartContextConfig = {
+}, t$8 = {
 	name: "treemap-chart",
 	label: "Treemap Chart",
 	synonyms: [
@@ -749,11 +931,11 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	},
 	description: "Creates a treemap chart. A treemap displays hierarchical data as nested rectangles, where the size of each rectangle\n    represents a value. Treemaps are effective for showing the composition of a whole and identifying patterns in hierarchical data.\n    They can display multiple levels of hierarchy. Use measure for the values and category for the hierarchy.\n    Color can be used to encode an additional dimension.",
 	slots: {
-		measure: { description: defaultMeasureDescription },
+		measure: { description: e$22 },
 		category: { description: "The column used as category in the chart. This determines the hierarchical structure and labels.\n        Typically this is a column with a type of hierarchy or datetime. Each category becomes a rectangle in the treemap." },
 		color: { description: "The column used as legend in the chart. Only add a legend if it is relevant to the chart.\n      This column is used in case of a second dimension to color the squares." }
 	}
-}, vennDiagramContextConfig = {
+}, e$20 = {
 	name: "venn-diagram",
 	label: "Venn Diagram",
 	synonyms: [
@@ -771,7 +953,7 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 		identifier: { description: "The column used as identifier in the diagram. This determines the items that belong to each set.\n        Typically this is a column with a type of hierarchy or categorical. This helps identify which items belong to which sets." },
 		measure: { description: "The column used as measure in the diagram. This determines the quantities or counts for each set intersection.\n        Typically a numeric column. This is optional and can be used to show the size of different intersections." }
 	}
-}, videoContextConfig = {
+}, e$21 = {
 	name: "video",
 	label: "Video",
 	synonyms: [
@@ -785,7 +967,7 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	},
 	description: "Creates a video element. A video element displays video content on a dashboard.\n    Video elements are effective for adding multimedia content, tutorials, or dynamic visual content to dashboards.\n    They work well for training materials, demonstrations, or engaging content.\n    Video elements can be configured with various playback and display options.",
 	slots: {}
-}, wordcloudChartContextConfig = {
+}, t$9 = {
 	name: "wordcloud-chart",
 	label: "Wordcloud Chart",
 	synonyms: [
@@ -800,9 +982,9 @@ const defaultMeasureDescription = "The column used as measure in the chart. If a
 	},
 	description: "Creates a wordcloud chart. A wordcloud displays text data where the size of each word represents its frequency or importance.\n    Wordclouds are effective for visualizing text data and identifying the most prominent terms or concepts.\n    They work well with text analysis, sentiment analysis, and content analysis. Use measure for the frequency/importance values\n    and category for the text labels. Color can be used to encode additional dimensions.",
 	slots: {
-		measure: { description: defaultMeasureDescription },
+		measure: { description: e$22 },
 		category: { description: "The column used as category in the chart. This determines the text labels for each word in the cloud.\n        Typically this is a column with a type of hierarchy or text. Each unique value becomes a word in the wordcloud." },
 		color: { description: "The column used to determine the color of words. Typically a categorical column.\n        Different categories are represented by different colors, allowing visualization of additional dimensions." }
 	}
 };
-export { areaChartContextConfig, barChartContextConfig, boxPlotContextConfig, bubbleChartContextConfig, bulletChartContextConfig, choroplethMapContextConfig, circlePackChartContextConfig, circularGaugeContextConfig, columnChartContextConfig, combinationChartContextConfig, conditionalNumberContextConfig, dateComparisonFilterContextConfig, dateFilterContextConfig, donutChartContextConfig, dropdownFilterContextConfig, evolutionNumberContextConfig, funnelChartContextConfig, heatMapContextConfig, heatTableContextConfig, hexbinMapContextConfig, imageContextConfig, lineChartContextConfig, markerMapContextConfig, ohlcChartContextConfig, parallelCoordinatesPlotContextConfig, pivotTableContextConfig, pyramidChartContextConfig, radarChartContextConfig, regularTableContextConfig, routeMapContextConfig, sankeyDiagramContextConfig, scatterPlotContextConfig, searchFilterContextConfig, slicerFilterContextConfig, sliderFilterContextConfig, speedometerChartContextConfig, spikeMapContextConfig, stripPlotContextConfig, sunburstChartContextConfig, symbolMapContextConfig, textContextConfig, treemapChartContextConfig, vennDiagramContextConfig, videoContextConfig, wordcloudChartContextConfig };
+export { t as areaChartContextConfig, t$1 as barChartContextConfig, e as boxPlotContextConfig, e$1 as bubbleChartContextConfig, a as bulletChartContextConfig, a$1 as choroplethMapContextConfig, a$2 as circlePackChartContextConfig, e$2 as circularGaugeContextConfig, a$3 as columnChartContextConfig, o as combinationChartContextConfig, e$3 as conditionalNumberContextConfig, e$4 as dateComparisonFilterContextConfig, e$5 as dateFilterContextConfig, a$4 as donutChartContextConfig, e$6 as dropdownFilterContextConfig, t$2 as evolutionNumberContextConfig, e$7 as funnelChartContextConfig, t$3 as heatMapContextConfig, t$4 as heatTableContextConfig, i as hexbinMapContextConfig, e$8 as imageContextConfig, t$5 as lineChartContextConfig, r as markerMapContextConfig, e$9 as ohlcChartContextConfig, e$10 as parallelCoordinatesPlotContextConfig, a$5 as pivotTableContextConfig, i$1 as pyramidChartContextConfig, e$11 as radarChartContextConfig, e$12 as regularTableContextConfig, e$13 as routeMapContextConfig, t$6 as sankeyDiagramContextConfig, e$14 as scatterPlotContextConfig, e$15 as searchFilterContextConfig, e$16 as slicerFilterContextConfig, e$17 as sliderFilterContextConfig, e$18 as speedometerChartContextConfig, s as spikeMapContextConfig, e$19 as stripPlotContextConfig, r$1 as sunburstChartContextConfig, s$1 as symbolMapContextConfig, t$7 as textContextConfig, t$8 as treemapChartContextConfig, e$20 as vennDiagramContextConfig, e$21 as videoContextConfig, t$9 as wordcloudChartContextConfig };