@getxflow/cli 0.20.0 → 0.20.2

package/dist/commands/projects.js

@@ -210,7 +210,7 @@ async function list() {
     const orgs = (0, credentials_1.listOrgs)(client.apiUrl);
     if (client.source === 'active' && orgs.length > 1) {
         const name = orgs.find((org) => org.active)?.name;
-        (0, ui_1.note)((0, ui_1.dim)(`  Projects of ${name ? `"${name}"` : 'the active organization'} alone: the rest of xflow org answer after org switch`));
+        (0, ui_1.note)((0, ui_1.dim)(`  Projects of ${name ? `"${name}"` : 'the active organization'} only. For another organization: xflow org switch <name or id>`));
     }
 }
 async function get(args) {

package/dist/help.js

@@ -175,13 +175,14 @@ project, the flag therefore goes somewhere else than the folder does. An id hand
 ${(0, ui_1.bold)('projects get')} or ${(0, ui_1.bold)('link')} behaves the same way: typed by hand, it is not redirected
 by a config lying around either.
 
-The id is echoed back on every run. It is the one place a project is named by hand,
-and a wrong id answers "not found" on a read but works on a write.
+The id is echoed back on every run, with the organization that holds the project. It
+is the one place a project is named by hand, and a wrong id answers "not found" on a
+read but works on a write.
 
 With several organizations signed in, the one holding the project is looked for on
 every call: there is no folder to write the answer into, and a second place to
-remember it would be a second thing to keep true. One ${(0, ui_1.bold)('xflow org switch')} to the
-right organization spares that search.`,
+remember it would be a second thing to keep true. When most calls go to one project,
+${(0, ui_1.bold)('xflow org switch')} to its organization skips that search.`,
     projects: `${(0, ui_1.bold)('xflow projects')}: the projects of the organization
 
   xflow projects list             every project, its versions state and age

package/dist/limits.js

@@ -62,6 +62,10 @@ function sizeLabel(mb) {
     return `${Number.isInteger(gb) ? String(gb) : gb.toFixed(1)} GB`;
 }
 function quotaValue(key, use) {
+    // null is a plan feature, not a missing number: the plan does not cap this.
+    if (use.limit === null) {
+        return key.endsWith('_mb') ? `${sizeLabel(use.used)} used, no limit` : `${use.used} used, no limit`;
+    }
     // Same unit on both sides: "0.2 of 15 GB", not "245 of 15360".
     if (key.endsWith('_mb')) {
         const used = use.limit >= 1000 ? (use.used / 1000).toFixed(1) : String(use.used);

package/dist/session.js

@@ -103,10 +103,6 @@ async function connectProject(projectId, root, config) {
             (0, ui_1.note)((0, ui_1.dim)(`  The project belongs to "${hit.name ?? hit.organizationId}", not to the active organization: the folder is bound to it`));
         }
     }
-    else if (hit.organizationId !== session.organizationId) {
-        // Nothing was written down, so the next command pays for the same search.
-        (0, ui_1.note)((0, ui_1.dim)(`  The project belongs to "${hit.name ?? hit.organizationId}": xflow org switch spares the next command this search`));
-    }
     return {
         apiUrl: session.apiUrl,
         token: hit.token,
@@ -144,11 +140,14 @@ async function projectTarget(args, options) {
         if (!isProjectId(named)) {
             throw new errors_1.CliError(`--project takes a project id, got "${named}"`, 'The ids: xflow projects list');
         }
+        const client = await connectProject(named, null);
         // Echoed back on every human run: the flag is the only place the id is typed by
-        // hand, and a wrong one answers 404 on a read and works on a write. Under --json
+        // hand, and a wrong one answers 404 on a read and works on a write. The
+        // organization is named too, since it may not be the active one. Under --json
         // the line is silenced with the rest, where the payload is the whole answer.
-        (0, ui_1.note)((0, ui_1.dim)(`  Project ${named} (--project)`));
-        return { projectId: named, client: await connectProject(named, null), root: null };
+        const org = (0, credentials_1.listOrgs)(client.apiUrl).find((entry) => entry.organizationId === client.organizationId);
+        (0, ui_1.note)((0, ui_1.dim)(`  Project ${named}${org ? ` of "${org.name ?? org.organizationId}"` : ''} (--project)`));
+        return { projectId: named, client, root: null };
     }
     const { root, config } = (0, config_1.requireProject)();
     const client = options?.probe === true ? await connectProject(config.projectId, root, config) : connect(config);

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.20.0';
+exports.CLI_VERSION = '0.20.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.20.0",
+  "version": "0.20.2",
   "description": "CLI for the XFlow platform: source sync, deployment and publishing of applications",
   "license": "UNLICENSED",
   "engines": {

package/skills/xflow/SKILL.md

@@ -22,7 +22,7 @@ contains the fix.
 
 ## Keeping these instructions current
 
-These instructions ship with xflow CLI 0.20.0, so the copy you are reading can be older than
+These instructions ship with xflow CLI 0.20.2, so the copy you are reading can be older than
 the CLI answering your commands.
 
 When the CLI says this file does not match it, run `xflow skills --refresh` and then **read
@@ -60,10 +60,11 @@ the error points away from the cause. The sections below carry the details.
 
 ## Plan limits
 
-The organization runs on a plan with finite limits: projects, databases, functions, active
+The organization runs on a plan with limits: projects, databases, functions, active
 connections, seats, database and file storage, function minutes, builds per month and at
-once, schedules and how often they may run. `xflow whoami` prints every one of them next to
-what is used, and the rights of your own key with them: destroying data in a migration,
+once, schedules and how often they may run. Most are finite; a plan may leave one uncapped,
+and then `whoami` prints `no limit` instead of a ceiling. `xflow whoami` prints every one of
+them next to what is used, and the rights of your own key with them: destroying data in a migration,
 deleting files from storage and linking a connected account each need a right that is off by
 default. Reading it before a long task turns a refusal halfway through the work into a
 sentence said before it starts.
@@ -150,6 +151,10 @@ Build setup:
 - Heavy media does not belong in the sources at all: the archive is capped at 10 MB and
   the built application at 15 MB unpacked. Upload it with `xflow storage push` instead
   and refer to the addresses it prints, see **File storage**.
+- Every file in the project is named with latin letters, digits, spaces and `. - _ ~`.
+  A name outside that set does not survive unpacking in the build sandbox, so `Größe.png`
+  and `логотип.png` break the build the same way. This is about the file name, not its
+  contents: interface text stays in whatever language the application speaks.
 
 Platform contract, checked across all of `src/`: