@getxflow/cli 0.11.0 → 0.11.1

package/dist/commands/db.js

@@ -177,14 +177,13 @@ async function dbQuery(args) {
     }
     (0, ui_1.table)([data.columns, ...data.rows.map((row) => data.columns.map((column) => cell(row[column])))]);
     if (data.truncated) {
-        // "raise --limit" used to be the whole advice, and for a long time it was
-        // impossible to follow: the ceiling and the default were the same number, so
-        // the flag could only ask for less. Now it can ask for more, and the line
-        // says so only while there is room left.
+        // No exact total here: the platform stops reading at limit + 1 rows, so all
+        // it knows is that more exist. The "raise --limit" advice shows only while
+        // the flag still has room below the ceiling.
         const room = data.limit !== undefined && data.limit_max !== undefined && data.limit < data.limit_max;
         (0, ui_1.note)((0, ui_1.dim)(room
-            ? `  Shown ${data.rows.length} of ${data.total}: raise --limit (up to ${data.limit_max}), or narrow the query`
-            : `  Shown ${data.rows.length} of ${data.total}: narrow the query, with a where clause or an offset`));
+            ? `  Shown the first ${data.rows.length} rows, more exist: raise --limit (up to ${data.limit_max}), or narrow the query`
+            : `  Shown the first ${data.rows.length} rows, more exist: narrow the query, with a where clause or an offset`));
     }
 }
 async function dbMigrate(args) {

package/dist/version.js

@@ -2,6 +2,6 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.DEFAULT_API_URL = exports.CLI_VERSION = void 0;
 /** Keep in sync with cli/package.json. */
-exports.CLI_VERSION = '0.11.0';
+exports.CLI_VERSION = '0.11.1';
 /** Overridden by XFLOW_API_URL or the `api` field in xflow.json. */
 exports.DEFAULT_API_URL = 'https://app.getxflow.com';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@getxflow/cli",
-  "version": "0.11.0",
+  "version": "0.11.1",
   "description": "CLI for the XFlow platform: source sync, deployment and publishing of applications",
   "license": "UNLICENSED",
   "engines": {

package/skills/xflow/SKILL.md

@@ -24,7 +24,7 @@ contains the fix.
 
 ## Keeping these instructions current
 
-These instructions ship with xflow CLI 0.11.0. They travel inside the package, so the copy
+These instructions ship with xflow CLI 0.11.1. They travel inside the package, so the copy
 you are reading can be older than the CLI answering your commands, and nothing about that
 is visible in the text itself.
 
@@ -235,6 +235,13 @@ enforces this, but a project where every function answers its own way costs an a
 on every call. Branch the frontend on `error.code`, never on `error.message`: wording
 gets rewritten on any edit, a code does not.
 
+How a non-2xx answer reaches the page depends on the generation of `src/lib/xflow.ts`
+in the project, so look at that file before writing the catch: a copy that declares
+`XFlowError` throws it carrying `code` and `status`, and a copy that says nothing about
+errors is older and throws a plain `Error` whose message is all there is. In an older
+project, a function that wants its error text seen on the page answers `200` with
+`{ success: false, error }` in the body.
+
 The sources are the whole truth about which functions exist. Delete the directory and the
 next deploy would delete the function from the cloud, schedules included, and that cannot be
 undone: a function created again later gets a different address. So never remove a function