@kong-ui-public/dashboard-renderer 8.12.15 → 8.12.16

package/README.md

@@ -16,7 +16,7 @@ Render Analytics charts on a page from a JSON definition.
   - [Tile Definition](#tile-definition)
   - [Chart Options](#chart-options)
   - [Chart Types](#chart-types)
-  - [Table Tile Configuration](#table-tile-configuration)
+  - [Table Chart Configuration](#table-chart-configuration)
   - [Common Chart Properties](#common-chart-properties)
   - [Query Configuration](#query-configuration)
   - [Time Range Configuration](#time-range-configuration)
@@ -29,7 +29,7 @@ Render Analytics charts on a page from a JSON definition.
 - A plugin providing an `AnalyticsBridge` must be installed in the root of the application.
   - This plugin must `provide` the necessary methods to adhere to the [AnalyticsBridge](https://github.com/Kong/public-ui-components/blob/main/packages/analytics/analytics-utilities/src/types/query-bridge.ts) interface defined in `@kong-ui-public/analytics-utilities`.
   - The plugin's query method is in charge of passing the query to the correct API for the host app's environment.
-  - For `table` tiles, the plugin must provide `tabularQueryFn`; the renderer passes a datasource-aware tabular query to that function and renders the returned records.
+  - For table chart tiles, the plugin must provide `tabularQueryFn`; the renderer passes a datasource-aware tabular query to that function and renders the returned records.
   - See the sandbox plugin [sandbox-query-provider.ts](https://github.com/Kong/public-ui-components/blob/main/packages/analytics/dashboard-renderer/sandbox/sandbox-query-provider.ts) for an example that simply returns static data rather than consuming an API.
 - The host application must supply peer dependencies for:
   - `@kong-ui-public/analytics-chart`
@@ -437,7 +437,7 @@ Configuration for individual dashboard tiles.
 
 ```typescript
 interface TileConfig {
-  type: 'chart' | 'table'      // The top-level tile kind
+  type: 'chart'                // The top-level tile kind
   definition: TileDefinition   // The tile's renderer-specific definition
   layout: TileLayout           // The tile's position and size in the grid
   id?: string                  // Optional unique identifier (required for editable dashboards)
@@ -448,15 +448,15 @@ interface TileConfig {
 Configuration for the renderer and query within a tile.
 
 ```typescript
-type TileDefinition = ChartTileDefinition | TableTileDefinition
+type TileDefinition = ChartTileDefinition | TableChartTileDefinition
 
 interface ChartTileDefinition {
-  chart: ChartOptions         // Configuration for the chart type and options
+  chart: ChartOptions         // Configuration for a non-table chart type and options
   query: ValidDashboardChartQuery  // Configuration for the chart data query
 }
 
-interface TableTileDefinition {
-  config: TableTileConfig     // Configuration for the table tile
+interface TableChartTileDefinition {
+  chart: TableChartOptions    // Configuration for the table chart
   query: PlatformTabularQuery & { datasource: 'platform' } // Configuration for the platform tabular query
 }
 ```
@@ -489,13 +489,14 @@ The following chart types are supported:
 
 Each chart type has its own configuration schema with specific options.
 
-### Table Tile Configuration
+### Table Chart Configuration
 
-Table tiles use `type: 'table'` on the tile itself. They are not chart tiles, so their definition uses `config` instead of `chart`.
+Table visuals are chart tiles with `type: 'chart'` on the tile itself and `definition.chart.type: 'table'`. Their `definition.query` uses the platform tabular query shape and renders through `TableDataGridRenderer`.
 
 ```typescript
-interface TableTileConfig {
-  title?: string
+interface TableChartOptions {
+  type: 'table'
+  chart_title?: string
 }
 
 interface PlatformTabularQuery {
@@ -507,18 +508,21 @@ interface PlatformTabularQuery {
 }
 ```
 
-`definition.query.columns` controls the visible table columns. If columns are omitted, the renderer can fall back to response `meta.columns` after the first tabular response. `definition.config.title` controls the tile title.
+`definition.query.columns` controls the visible table columns. If columns are omitted, the renderer can fall back to response `meta.columns` after the first tabular response. `definition.chart.chart_title` controls the tile title.
 
 The dashboard config query includes `datasource: 'platform'`. The host application's `AnalyticsBridge.tabularQueryFn` receives a datasource-aware tabular query, currently `{ datasource: 'platform', query: { entity, columns, filters, page_size, cursor } }`.
 
 The renderer replaces raw record values with display labels when the tabular response includes a matching `meta.display[column][value].name`. Missing display entries and `null` values are rendered unchanged.
 
+Table charts do not expose CSV export or API Requests links. They may expose Explore links when the host application provides the Explore context-link bridge.
+
 ```typescript
 const tableTile: TileConfig = {
-  type: 'table',
+  type: 'chart',
   definition: {
-    config: {
-      title: 'Platform routes',
+    chart: {
+      type: 'table',
+      chart_title: 'Platform routes',
     },
     query: {
       datasource: 'platform',
@@ -575,7 +579,7 @@ Chart query fields include:
 - `granularity`: Time bucket size for temporal queries
 - `limit`: Number of results to return
 
-Table tile queries use the platform tabular query shape:
+Table chart queries use the platform tabular query shape:
 - `datasource`: Must be `platform`
 - `entity`: Entity collection to query, such as `route`
 - `columns`: Ordered table columns to request and render

package/dist/{GeoMapRenderer-azbs6_67.js → GeoMapRenderer-CDCvLcNv.js}

@@ -1,5 +1,5 @@
 import { defineComponent as q, ref as C, computed as c, openBlock as x, createBlock as g, withCtx as _, createVNode as E, unref as M } from "vue";
-import { _ as O } from "./index-B-sUo98c.js";
+import { _ as O } from "./index-DxrhvuyE.js";
 import { exploreResultToCountryMetrics as b, AnalyticsGeoMap as k } from "@kong-ui-public/analytics-geo-map";
 import { COUNTRIES as B } from "@kong-ui-public/analytics-utilities";
 const R = /* @__PURE__ */ q({

package/dist/dashboard-renderer.es.js

@@ -1,4 +1,4 @@
-import { C as a, D as R, a as T, b as s, c as L, d as I, E as e, F as D, e as N, G as S, I as r, T as A, f as F } from "./index-B-sUo98c.js";
+import { C as a, D as R, a as T, b as s, c as L, d as I, E as e, F as D, e as N, G as S, I as r, T as A, f as F } from "./index-DxrhvuyE.js";
 export {
   a as CP_ID_TOKEN,
   R as DASHBOARD_COLS,