@lightdash/cli 1.84.0 → 1.85.0

package/dist/index.js

@@ -10,6 +10,7 @@ const error_1 = require("./error");
 const globalState_1 = tslib_1.__importDefault(require("./globalState"));
 const createApp_1 = require("./handlers/apps/createApp");
 const preview_1 = require("./handlers/apps/preview");
+const validate_1 = require("./handlers/apps/validate");
 const compile_1 = require("./handlers/compile");
 const connectSnowflake_1 = require("./handlers/connectSnowflake");
 const refresh_1 = require("./handlers/dbt/refresh");
@@ -33,7 +34,7 @@ const runChart_1 = require("./handlers/runChart");
 const setProject_1 = require("./handlers/setProject");
 const setWarehouse_1 = require("./handlers/setWarehouse");
 const sql_1 = require("./handlers/sql");
-const validate_1 = require("./handlers/validate");
+const validate_2 = require("./handlers/validate");
 const warehouseCatalog_1 = require("./handlers/warehouseCatalog");
 const styles = tslib_1.__importStar(require("./styles"));
 // Trigger CLI tests
@@ -446,6 +447,15 @@ appsProgram
     .option('--port <port>', 'port for the app dev server (default: Vite picks one, usually 5173)')
     .option('--verbose', undefined, false)
     .action(preview_1.appsPreviewHandler);
+appsProgram
+    .command('validate [paths...]')
+    .description('Validate data app source, manifests, dependencies, and semantic-layer references locally.')
+    .option('--live', 'Validate against fresh explores from each app project instead of its downloaded semantic-layer snapshot.', false)
+    .addOption(new commander_1.Option('--format <format>', 'Output format: human or json')
+    .choices(['human', 'json'])
+    .default('human'))
+    .option('--verbose', undefined, false)
+    .action(validate_1.appsValidateHandler);
 commander_1.program
     .command('deploy')
     .description('Compiles and deploys a Lightdash project')
@@ -529,7 +539,7 @@ commander_1.program
     .option('--include-spaces <spaceSlugs...>', 'Only report validation errors for charts and dashboards in these spaces (and their sub-spaces). Spaces must be visible to your credentials')
     .option('--exclude-spaces <spaceSlugs...>', 'Skip validation errors for charts and dashboards in these spaces (and their sub-spaces). Spaces must be visible to your credentials')
     .option('--no-partial-compilation', 'Fail when a field or join cannot be compiled instead of returning a partial explore')
-    .action(validate_1.validateHandler);
+    .action(validate_2.validateHandler);
 commander_1.program
     .command('generate')
     .description('Generates a new schema.yml file for model')

package/dist/vendor/authoring/README.md.tmpl

@@ -4,9 +4,10 @@ Created or downloaded with the Lightdash CLI.
 
 ## Edit → build → upload
 1. Edit files under `src/`.
-2. Optionally, run `npm run build` to check it compiles locally. `lightdash apps create` installs the initial dependencies after asking permission; after `lightdash download`, run `npm install` first if `node_modules` is absent. If the local install or build fails in your environment, treat it as a non-blocking warning and continue to upload. Keep the failure details because they may predict a server build problem, but don't change machine or registry config to force the pre-check to pass — the server build on upload is authoritative and surfaces its result on the app page.
-3. Optionally, preview against real data: `lightdash apps preview` (needs a successful `npm install`).
-4. `lightdash upload --apps <slug>` (the `slug` from `lightdash-app.yml`) — Lightdash rebuilds and serves the app.
+2. Run `lightdash apps validate` to check the source, manifest, dependencies, external-connection aliases, and semantic references against the downloaded context. Use `--live` for fresh project explores or `--format json` in CI.
+3. Optionally, run `npm run build` to check it compiles locally. `lightdash apps create` installs the initial dependencies after asking permission; after `lightdash download`, run `npm install` first if `node_modules` is absent. If the local install or build fails in your environment, treat it as a non-blocking warning and continue to upload. Keep the failure details because they may predict a server build problem, but don't change machine or registry config to force the pre-check to pass — the server build on upload is authoritative and surfaces its result on the app page.
+4. Optionally, preview against real data: `lightdash apps preview` (needs a successful `npm install`).
+5. `lightdash upload --apps <slug>` (the `slug` from `lightdash-app.yml`) — Lightdash rebuilds and serves the app.
 
 Local preview uses your existing CLI login through a project- and route-restricted loopback proxy; the credential is not written into this folder or exposed to browser code. It runs local tooling as your OS user (with access to that user's files, including the existing CLI config) and shows data under your own permissions, so preview only source/dependencies you trust. Host-mediated features such as external connections and data-app-viz context still need testing after upload.
 

package/dist/vendor/authoring/developing-data-apps-locally/SKILL.md

@@ -28,8 +28,9 @@ You are editing a Lightdash **data app** that was created or downloaded with the
 ## The edit → build → upload loop
 
 1. Edit files under `src/` only.
-2. Optionally, run `npm run build` to check it compiles. Apps made with `lightdash apps create` already have their initial dependencies installed. After `lightdash download`, if you choose to do the local pre-check and `node_modules` is absent, run `npm install` first. This is an **optional local pre-check** — see below.
-3. `lightdash upload --apps <slug>` (the `slug` from this folder's `lightdash-app.yml`) — the **server** rebuilds and serves the app. The server rebuild, not your local build, is what ships.
+2. Run `lightdash apps validate` to check the source, manifest, dependencies, external-connection aliases, and semantic references against the downloaded context. Use `--live` to check against fresh project explores; use `--format json` in CI. A green run reports any call sites it could not fully analyze instead of silently claiming complete coverage.
+3. Optionally, run `npm run build` to check it compiles. Apps made with `lightdash apps create` already have their initial dependencies installed. After `lightdash download`, if you choose to do the local pre-check and `node_modules` is absent, run `npm install` first. This is an **optional local pre-check** — see below.
+4. `lightdash upload --apps <slug>` (the `slug` from this folder's `lightdash-app.yml`) — the **server** rebuilds and serves the app. The server rebuild, not your local build, is what ships.
 
 ## The local build is optional — never fight a failing install
 

package/dist/vendor/template/references/chart-references.md

@@ -139,6 +139,7 @@ generation, so author them normally.)
 **Important:** The field IDs in metric queries use qualified names (e.g.,
 `orders_total_revenue`). When mapping to SDK calls:
 - **Base explore fields:** Strip the explore name prefix. `orders_total_revenue` → `total_revenue`
+  - **Prefix-collision exception:** If the remaining short name still begins with the explore name and an underscore, keep the original qualified ID. For example, `custom_roles_custom_roles_created` must stay fully qualified; shortening it to `custom_roles_created` makes the SDK mistake it for an already-qualified ID.
 - **Joined table fields:** Convert to dot notation. If the explore is `orders` and the field is
   `customers_customer_name`, that's a joined table field — use `customers.customer_name`.
   **Only strip the prefix if it matches the explore name.** If it doesn't match, it's a joined table.

package/dist/vendor/template/skill.md

@@ -226,7 +226,11 @@ export function RevenueBySegment() {
 
 ### Field names
 
-Use **short names** like `total_revenue`, not qualified names like `orders_total_revenue`. The SDK qualifies them automatically. For joined table fields, use **dot notation** like `customers.name` (see "Joined table fields" above).
+Use **short names** like `total_revenue` for base-explore fields; the SDK qualifies them automatically. Already-qualified base field IDs such as `orders_total_revenue` are also accepted.
+
+There is one important ambiguity: if a base field's short name already begins with the explore name and an underscore, keep its **fully qualified ID**. For example, the `custom_roles_created` metric on the `custom_roles` explore must be passed as `custom_roles_custom_roles_created`. Passing the short name would be mistaken for an already-qualified ID and sent to the API unchanged. Query result keys match the identifier passed to the builder, so use that same fully qualified ID when reading rows or calling `format`.
+
+For joined table fields, use **dot notation** like `customers.name` (see "Joined table fields" above).
 
 ### Query builder
 
@@ -1182,7 +1186,7 @@ The action-menu example above shows typical `drillDown()` usage. For the full AP
 | Unused dimensions in `.dimensions()` | Changes GROUP BY → wrong numbers | Only include dimensions you render |
 | Querying hidden fields (`customer_id`) | Leaks internal IDs | Skip fields with `hidden: true` |
 | Calling `createClient()` in app code | Not needed — client is set up in `main.jsx` | `import { query, useLightdash } from '@lightdash/query-sdk'` |
-| Qualified names like `orders_total_revenue` | Double-qualified → unknown field | Short names only |
+| Short base field name starts with the explore prefix: `query('custom_roles').metrics(['custom_roles_created'])` | Mistaken for an already-qualified ID → unknown field | Preserve the full ID: `custom_roles_custom_roles_created` |
 | Joined table field without dot notation: `customer_name` | Resolves to `orders_customer_name` → unknown field | Use `customers.customer_name` for joined tables |
 | `value: '2025'` for a number column | String won't match number | `value: 2025` |
 | Not filtering on grain dimensions you don't render | Duplicates, mixed data, wrong totals | Identify the grain, filter dimensions you don't display |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lightdash/cli",
-  "version": "1.84.0",
+  "version": "1.85.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.84.0",
-    "@lightdash/warehouses": "1.84.0"
+    "@lightdash/common": "1.85.0",
+    "@lightdash/warehouses": "1.85.0"
   },
   "devDependencies": {
     "@types/inquirer": "8.2.4",