@myapihq/cli 2.31.2 → 2.31.3

package/dist/flags.js

@@ -22,6 +22,9 @@ export const GLOBAL_FLAGS = {
     version: 'boolean',
     org: 'string',
 };
+// Value flags that name one target rather than a list, mapped to the noun used
+// when refusing a duplicate. Comma-separating these is not a workaround.
+const SINGLE_VALUED = new Map([['org', 'organisation']]);
 // Short aliases are consumed as `-h` / `-v` / `-V` before the `--flag` branch,
 // so they never appear as keys in `merged` and need no type — but they do land
 // in `flags` (as help/version), so the dispatcher must still tolerate them.
@@ -134,10 +137,20 @@ export function parseFlags(argv, schema = {}, quiet = false) {
             // mistake when the docs say "comma-separated"; silently honouring the
             // last is the one behaviour that can't be recovered from. Refuse, and
             // say what to do instead.
+            //
+            // The comma-separated suggestion is right for a flag that names a list of
+            // things and wrong for one that names a single target: a command writes to
+            // one organisation, so `--org a,b` would just build an id that matches no
+            // org. Say which case this is rather than offering advice that cannot work.
             if (seenValueFlags.has(key)) {
-                throw new Error(`--${key} was given more than once. Only the last value would be used, ` +
-                    `which silently discards the others.\n` +
-                    `→ If you meant to pass several values, comma-separate them: --${key} a,b,c`);
+                const previous = flags[key];
+                throw new Error(SINGLE_VALUED.has(key)
+                    ? `--${key} was given more than once ("${String(previous)}", then "${raw}"). ` +
+                        `Only the last would be used, which silently discards the first.\n` +
+                        `→ A command acts on one ${SINGLE_VALUED.get(key)}. Pass --${key} once.`
+                    : `--${key} was given more than once. Only the last value would be used, ` +
+                        `which silently discards the others.\n` +
+                        `→ If you meant to pass several values, comma-separate them: --${key} a,b,c`);
             }
             seenValueFlags.add(key);
             if (type === 'number') {

package/dist/flags.test.js

@@ -206,6 +206,19 @@ describe('global flag lists cannot drift', () => {
         // other nineteen silently kept the last value. Parse with an empty schema
         // to stand in for a command that declares nothing of its own.
         expect(() => parseFlags(['--org', 'ORG_A', '--org', 'ORG_B'], {}, true)).toThrow(/--org was given more than once/);
+        // The generic advice ("comma-separate them") cannot work for org: a command
+        // writes to one organisation, and --org a,b is just an id that matches none.
+        let msg = '';
+        try {
+            parseFlags(['--org', 'ORG_A', '--org', 'ORG_B'], {}, true);
+        }
+        catch (e) {
+            msg = e.message;
+        }
+        expect(msg).not.toContain('comma-separate');
+        expect(msg).toContain('acts on one organisation');
+        expect(msg).toContain('ORG_A');
+        expect(msg).toContain('ORG_B');
     });
     it('a single --org still parses to its value under an empty schema', () => {
         const { flags } = parseFlags(['--org', 'ORG_A'], {}, true);

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@myapihq/cli",
   "license": "Apache-2.0",
-  "version": "2.31.2",
+  "version": "2.31.3",
   "description": "MyAPI command-line interface",
   "repository": {
     "type": "git",
@@ -47,7 +47,7 @@
     "lint:skills:strict": "node scripts/copy-skills.js && node scripts/lint-skills.js --strict"
   },
   "dependencies": {
-    "@myapihq/sdk": "^2.31.2"
+    "@myapihq/sdk": "^2.31.3"
   },
   "devDependencies": {
     "@types/node": "^25.6.0",