@lightdash/cli 1.5.1 → 1.7.0

package/dist/vendor/template/skill.md

@@ -184,13 +184,13 @@ const revenueQuery = query('orders')
     .limit(10);
 
 export function RevenueBySegment() {
-    const { data, format, loading, error } = useLightdash(revenueQuery);
+    const { data, format, loading, error, lineage } = useLightdash(revenueQuery);
 
     if (loading) return <p className="text-sm text-muted-foreground">Loading...</p>;
     if (error) return <p className="text-sm text-destructive">Error: {error.message}</p>;
 
     return (
-        <div className="space-y-2">
+        <div className="space-y-2" {...lineage}>
             {data.map((row, i) => (
                 <div key={i} className="flex justify-between">
                     <span>{format(row, 'customer_segment')}</span>
@@ -297,6 +297,7 @@ If the dbt YAML declares a `parameters:` block (under a model's `meta:` / `confi
 | `totalResults` | `number \| null` | Total rows returned by the loaded source query. Use for export labels/counts. |
 | `loading` | `boolean` | True while query is in flight. |
 | `error` | `Error \| null` | Query error. |
+| `lineage` | `LineageProps` | **Spread on the root element of every rendered query block** (`<div {...lineage}>`). Stamps the block so the host's Inspect data button can trace it back to this query — without it that button stays disabled. |
 | `refetch` | `() => void` | Re-run the query on demand. |
 | `queryUuid` | `string \| null` | The async Lightdash query UUID for the loaded source query. Rarely needed directly. |
 | `getUnderlyingData` | `({ row, metric, limit? }) => Promise<{ rows, columns, format, queryUuid }>` | Fetch raw rows behind an aggregated metric value. Call from a user action, never on initial render. |
@@ -717,10 +718,10 @@ import { Card, CardHeader, CardTitle, CardContent } from '@/components/ui/card';
 import { Alert, AlertDescription } from '@/components/ui/alert';
 
 export function RevenueCard() {
-    const { data, format, loading, error } = useLightdash(revenueQuery);
+    const { data, format, loading, error, lineage } = useLightdash(revenueQuery);
 
     return (
-        <Card>
+        <Card {...lineage}>
             <CardHeader>
                 <CardTitle>Revenue</CardTitle>
             </CardHeader>
@@ -792,8 +793,8 @@ export function RevenueBySegment() {
         () => baseRevenueQuery.filters(filtersFor(EXPLORE)),
         [filtersFor],
     );
-    const { data, format, loading } = useLightdash(q);
-    // ...
+    const { data, format, loading, lineage } = useLightdash(q);
+    // ...spread {...lineage} on the block's root element
 }
 ```
 
@@ -1143,6 +1144,8 @@ The action-menu example above shows typical `drillDown()` usage. For the full AP
 | `.limit()` too low | Silently truncates rows — charts end early, tables incomplete | Estimate row count from the grain, set limit above that |
 | Building queries inside render | Infinite re-fetching | Define queries at module scope or memoize them |
 | Forgetting to apply global filters to a query | Chart shows unfiltered data while the rest of the page is filtered → contradictory results | Every `useLightdash()` call must pass `filtersFor(EXPLORE)` into `.filters([...])` via `useMemo` |
+| Forgetting to spread `lineage` on a query block | The host's Inspect data button stays disabled for that block | Destructure `lineage` from `useLightdash()` and spread it on the block's root element |
+| Spreading `lineage` onto a component that swallows unknown props | The stamp never reaches the DOM, so the block looks wired but Inspect data still can't trace it | Spread onto a plain element (`<div {...lineage}>`) or a component that forwards rest props to its root element (all `@/components/ui` primitives do) |
 | Calling `addFilter` without an `explore` tag | Filter has no explore → the `filtersFor(otherExplore)` lookup never returns it, or (worse) you broadcast it everywhere → `FieldReferenceError` like `regional_sales_status` not found | Always include `explore: EXPLORE` on every `addFilter` call |
 | Using `filters` (raw) instead of `filtersFor(EXPLORE)` | Sends filters from other explores into this query → SDK qualifies the field name to the wrong explore → `FieldReferenceError` | Always select via `filtersFor(EXPLORE)`; never pass `allFilters` into `.filters()` |
 | Hard-coding the explore string in two places | Chart and its action menu disagree → filter sets but never applies | Define `const EXPLORE = '...'` at the top of the file and reuse it for both `query(EXPLORE)` and `addFilter({ ..., explore: EXPLORE })` |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lightdash/cli",
-  "version": "1.5.1",
+  "version": "1.7.0",
   "description": "Lightdash CLI tool",
   "license": "MIT",
   "repository": {
@@ -41,8 +41,8 @@
     "unique-names-generator": "4.7.1",
     "uuid": "11.1.1",
     "yaml": "2.8.3",
-    "@lightdash/common": "1.5.1",
-    "@lightdash/warehouses": "1.5.1"
+    "@lightdash/common": "1.7.0",
+    "@lightdash/warehouses": "1.7.0"
   },
   "devDependencies": {
     "@types/inquirer": "8.2.4",