@erdoai/cli 0.139.0 → 0.139.1

package/dist/index.js

@@ -1223,6 +1223,9 @@ var ErdoClient = class {
   getDatasetDeclaredSchema(slug) {
     return this.request("POST", `/v1/datasets/${encodeURIComponent(slug)}/fetch`, { view: "declared_schema" });
   }
+  getDatasetResourceSchema(slug) {
+    return this.request("POST", `/v1/datasets/${encodeURIComponent(slug)}/fetch`, { view: "resource_schema" });
+  }
   // Create an empty dataset with its declared columns. The server refuses a
   // create without a schema unless the purpose's columns are platform-defined.
   createDataset(input) {
@@ -7281,7 +7284,7 @@ Read one with: erdo datasets fetch ${res.dataset_slug} --revision <id> --sql "SE
   }
 });
 datasetsCmd.command("schema <slug>").alias("describe").description(
-  "Show physical columns by default, or the declared write contract with --declared. Physical columns are the names and types you can reference in `datasets fetch --sql`, read from the stored `data` table itself (DuckDB DESCRIBE) so they are what is actually there, not what was declared. For a database or warehouse dataset, DESCRIBE its real table names instead: `datasets fetch <slug> --sql 'DESCRIBE <table>'`."
+  "Show physical columns by default, or the declared write contract with --declared. File datasets read the stored `data` table; integration datasets show their discovered resource tables and columns. For an integration dataset, choose a resource/table explicitly when fetching: `datasets fetch <slug> --sql 'SELECT * FROM <table>'`."
 ).option("--json", "print the raw JSON result instead of a table").option("--declared", "read the declared write contract (column names, type hints, required flags, semantic roles) instead of the physical columns").action(async (slug, opts) => {
   try {
     const client = new ErdoClient();
@@ -7310,7 +7313,35 @@ datasetsCmd.command("schema <slug>").alias("describe").description(
       );
       return;
     }
-    const res = await client.fetchDatasetContents(slug, { sql_query: "DESCRIBE data" });
+    const res = await client.getDatasetResourceSchema(slug);
+    if (!res || typeof res !== "object" || res.view !== "resource_schema")
+      throw new Error("Invalid dataset schema response: the server did not answer the resource_schema view");
+    if (res.schema_provenance === "resource_catalog") {
+      const resources = res.resources ?? [];
+      if (!Array.isArray(resources) || resources.some((resource) => !resource || !Array.isArray(resource.columns)))
+        throw new Error("Invalid dataset schema response: malformed resource catalog");
+      if (opts.json) {
+        print(res);
+        return;
+      }
+      if (!resources.length) {
+        console.log(`${slug} has no discovered integration resources yet.`);
+        return;
+      }
+      const rows = resources.flatMap(
+        (resource) => resource.columns.length ? resource.columns.map((column) => [
+          resource.table_name || resource.key || resource.name,
+          column.name,
+          column.type || ""
+        ]) : [[resource.table_name || resource.key || resource.name, "", "(columns unavailable)"]]
+      );
+      printAlignedTable(["table", "column", "type"], rows);
+      console.log(`
+Fetch a selected table with: erdo datasets fetch ${slug} --sql "SELECT * FROM <table>"`);
+      return;
+    }
+    if (res.schema_provenance !== "dataset_storage" || !Array.isArray(res.columns) || !Array.isArray(res.rows))
+      throw new Error("Invalid dataset schema response: malformed physical schema");
     if (opts.json) {
       print(res);
       return;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@erdoai/cli",
-  "version": "0.139.0",
+  "version": "0.139.1",
   "description": "Erdo CLI \u2014 drive datasets, pages, and evals from the terminal or CI",
   "type": "module",
   "bin": {