@getxflow/cli 0.14.1 → 0.14.2

package/dist/flags.js

@@ -1,6 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.KNOWN = void 0;
+exports.WORKING_COPY = exports.KNOWN = void 0;
 exports.checkFlags = checkFlags;
 const args_1 = require("./args");
 const errors_1 = require("./errors");
@@ -19,8 +19,8 @@ const help_1 = require("./help");
  *
  * `--project` is a flag like any other here, and it is written against a command
  * only when that command can answer without the working copy. The ones that cannot
- * (deploy, pull, status, db migrate, env check, env set, connections unlink) have
- * a folder to stand in, and naming a project they cannot read would be a lie.
+ * have a folder to stand in, and naming a project they cannot read would be a lie;
+ * they are listed in WORKING_COPY below, each with what it reads from that folder.
  * `db status` sits halfway: named by id it answers with the applied history alone,
  * without the comparison against migrations/.
  *
@@ -87,6 +87,27 @@ exports.KNOWN = {
     deployments: ['project'],
     update: [],
 };
+/**
+ * What each of those commands reads from the working copy, in its own words.
+ *
+ * `has no flag --project` alone leaves the reader one dead end short of the answer:
+ * the next try, without the flag, ends at the missing xflow.json, and neither line
+ * tells a rule from an oversight. Naming the file the command would have to read
+ * does, and it also says when the errand needs no folder at all.
+ *
+ * Keys are the commands KNOWN keeps `--project` from, and flags.test.ts holds the
+ * two lists against each other: a command that later gains the flag has to lose its
+ * line here, or a refusal nobody prints any more stays behind as a lie.
+ */
+exports.WORKING_COPY = {
+    deploy: 'it sends the sources next to it',
+    pull: 'it writes the sources next to it',
+    status: 'it compares the folder with the revision on the platform',
+    'db migrate': 'it applies the files of migrations/',
+    'env check': 'it looks for the variables the code of the functions reads',
+    'env set': 'it names the functions that need a deploy for the value to arrive',
+    'connections unlink': 'it reads functions/ to name the functions that would lose the variables. Only trying an API out? That needs no link: xflow connections call',
+};
 /** Answered everywhere: both are handled before the command runs. */
 const GLOBAL = new Set(['help', 'version']);
 /**
@@ -118,6 +139,15 @@ function commandOf(words) {
     }
     return Object.hasOwn(exports.KNOWN, first) ? first : null;
 }
+function hintFor(command, flag, allowed, page) {
+    const reads = exports.WORKING_COPY[command];
+    if (flag === 'project' && reads !== undefined) {
+        return `It works in the project folder: ${reads}. Which commands take --project: xflow help project`;
+    }
+    return allowed.length > 0
+        ? `It takes ${allowed.map((name) => `--${name}`).join(', ')}. What each one does: ${page}`
+        : `It takes no flags. What it does: ${page}`;
+}
 function checkFlags(args) {
     const command = commandOf(args.words);
     if (command === null)
@@ -131,9 +161,7 @@ function checkFlags(args) {
         if (GLOBAL.has(name))
             continue;
         if (!allowed.includes(name)) {
-            throw new errors_1.CliError(`xflow ${command} has no flag --${name}`, allowed.length > 0
-                ? `It takes ${allowed.map((flag) => `--${flag}`).join(', ')}. What each one does: ${page}`
-                : `It takes no flags. What it does: ${page}`);
+            throw new errors_1.CliError(`xflow ${command} has no flag --${name}`, hintFor(command, name, allowed, page));
         }
         // The value went missing, so the flag arrived as a bare switch. Left alone it
         // would mean the default, which is never what the person typing it wanted.

package/dist/help.js

@@ -381,7 +381,9 @@ of the same service under one name; then the command prints their identifiers an
 for one of those instead of guessing.
 
 ${(0, ui_1.bold)('unlink')} refuses while a function still reads one of the variables and names
-those functions; ${(0, ui_1.bold)('--force')} goes through anyway.
+those functions; ${(0, ui_1.bold)('--force')} goes through anyway. Seeing them needs the sources,
+which is why ${(0, ui_1.bold)('unlink')} works in the project folder and takes no ${(0, ui_1.bold)('--project')}
+while ${(0, ui_1.bold)('link')} takes it: only one of the two reads your code.
 
 Variables are named after the alias: an OAuth connection called ${(0, ui_1.bold)('YANDEX_METRIKA')}
 gives ${(0, ui_1.bold)('YANDEX_METRIKA_TOKEN')}, a key-based one gives a variable per field. They

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.14.1';
+exports.CLI_VERSION = '0.14.2';
 /** 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.14.1",
+  "version": "0.14.2",
   "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.14.1. They travel inside the package, so the copy
+These instructions ship with xflow CLI 0.14.2. 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.
 
@@ -360,8 +360,9 @@ unavailable: the account you need is often connected already, one link away.
 
 `xflow connections link "Яндекс Метрика" --as YANDEX_METRIKA` is that link and
 `xflow connections unlink YANDEX_METRIKA` undoes it; `xflow help connections` has the
-naming rules and the flags. Unlink refuses while a function still reads one of the
-variables and names those functions, so read that list before reaching for `--force`.
+naming rules and the flags. Unlink reads `functions/`, so it runs in the project folder:
+it refuses while a function still reads one of the variables and names those functions,
+so read that list before reaching for `--force`.
 
 Linking needs the `connections:link` right on the key, and only accounts granted to the
 owner of the key personally can be linked at all; the same right covers calling an unlinked