@koda-sl/baker-cli 0.354.0-dev.e6a354971 → 0.354.0

package/README.md

@@ -98,12 +98,7 @@ All commands return a JSON envelope:
 ### Unknown options are refused
 
 An option a command does not declare stops the run with `UNKNOWN_ARGUMENT`, naming the
-real one it was most likely reaching for, with the first sentence of that option's own
-description. A word the command spells differently is matched by meaning (`--from` and
-`--since` → `--start-date`, `--to` and `--until` → `--end-date`, `--path` and `--url` →
-`--landing`, each only where the command has it); otherwise only a near spelling is
-offered, so a short option is never pointed at an unrelated one (`--from` at `--full`).
-Previously such an option was accepted and ignored, so a call that
+closest real one. Previously such an option was accepted and ignored, so a call that
 looked like it had filtered or narrowed a result was in fact answering the unfiltered
 question — and nothing in the output said so. Both spellings of an option work
 (`--run-id` and `--runId`), as they always did. The error's `fix` names the exact call
@@ -747,7 +742,7 @@ Use `--no-cache` on any command to bypass **both** the local file cache and the
 |------|-----------|---------|
 | `FIELD_NOT_FOUND` | No | Invalid field in GAQL query |
 | `WRONG_RESOURCE` | No | Field queried from wrong resource |
-| `INVALID_OPERATOR` | No | Unsupported operator (e.g. CONTAINS) |
+| `INVALID_OPERATOR` | No | Unsupported operator (e.g. CONTAINS(), or =, IN or IS NOT NULL on a list field such as `final_urls` or `labels`, which takes only CONTAINS ALL/ANY/NONE). List-field operators are refused before the query is sent, with a corrected command that rewrites =/IN to CONTAINS ANY and drops a null test |
 | `CUSTOMER_NOT_FOUND` | No | Invalid customer ID — run `baker ads google accounts` to find valid IDs |
 | `MISSING_MANAGER_ID` | No | Account not accessible (may need MCC login-customer-id) |
 | `INCOMPATIBLE_FIELDS` | No | Fields can't be in same query |
@@ -1338,7 +1333,7 @@ Shared flags: `--days <n>` (default 30) or `--start-date` / `--end-date` (`YYYY-
 
 `--measure` decides whose activity is measured and defaults to `campaigns` (only visitors a Baker landing brought). `--measure all` measures the client's entire website and is a decision somebody has to ask for. `host` is the client's own landing domain when one shares a domain with the site being measured, so the script and its events stay first-party; `firstParty` in the response says which, and removing that domain from Baker means re-running this command.
 
-**Paging the list reports.** `people`, `submissions` and `delivery` are lists of individual things rather than breakdowns — `delivery` and `submissions` are the ones the CLI exposes, `people` backs the People section of the dashboard's landing Analytics screen over the same wire — and only they take `--page <n>` (1-based) and `--page-size <n>` (up to 200, default 50). The response carries `pageInfo` with `hasMore` — when it is true there **are** more rows, so a total must never be reported from one page. Pass neither flag and a list comes back at the size it always did. A value that is not a whole positive number (`--page /pricing`) is refused before any request, naming `--landing` as the flag that narrows a report to one page of the site.
+**Paging the list reports.** `people`, `submissions` and `delivery` are lists of individual things rather than breakdowns — `delivery` and `submissions` are the ones the CLI exposes, `people` backs the People section of the dashboard's landing Analytics screen over the same wire — and only they take `--page <n>` (1-based) and `--page-size <n>` (up to 200, default 50). The response carries `pageInfo` with `hasMore` — when it is true there **are** more rows, so a total must never be reported from one page. Pass neither flag and a list comes back at the size it always did.
 
 **A conversion is a company-level named event, not a property of a Form.** `baker analytics conversions` is the only place "what counts" is decided, and an empty `definitions` list means every conversion number in every other report is zero — not because nobody converted, but because nothing is named as an outcome and Baker never guesses which event is the point of a page. `--candidates` lists every event these pages actually produced — each Form step and trigger, every `data-baker-*` event, every outbound destination — with volume and whether it is already counted; that list is where an event key comes from, so never invent one. `--event <key> --name "Booked a call"` starts counting it **immediately and retroactively**: the whole stored history is rescored, so naming the right event today also fixes last month. Nothing here is staged and publishing is not involved. Two events given the same `--name` become one row and one number, which is how a call booked on three different Forms reads as one outcome. `--count-mode every_time` is for the outcomes people genuinely repeat (a guide downloaded twice is two downloads); the default counts once per visit.
 

package/dist/{chunk-B7MLH3K6.js → chunk-4HRJQGVW.js}

@@ -20,9 +20,9 @@ import {
   shouldEscalate
 } from "./chunk-2OKSJNLA.js";
 
-// ../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/766ad107c42df28eeadaf0ac2f9089c8a9e200f6ba0b2b1a817b8d536cbdcc49/node_modules/safe-stable-stringify/index.js
+// ../../node_modules/.pnpm/safe-stable-stringify@2.5.0/node_modules/safe-stable-stringify/index.js
 var require_safe_stable_stringify = __commonJS({
-  "../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/766ad107c42df28eeadaf0ac2f9089c8a9e200f6ba0b2b1a817b8d536cbdcc49/node_modules/safe-stable-stringify/index.js"(exports, module) {
+  "../../node_modules/.pnpm/safe-stable-stringify@2.5.0/node_modules/safe-stable-stringify/index.js"(exports, module) {
     "use strict";
     var { hasOwnProperty } = Object.prototype;
     var stringify = configure2();
@@ -1114,7 +1114,7 @@ function resolveAdaptFormats(params) {
   return params.formats ?? [];
 }
 
-// ../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/766ad107c42df28eeadaf0ac2f9089c8a9e200f6ba0b2b1a817b8d536cbdcc49/node_modules/safe-stable-stringify/esm/wrapper.js
+// ../../node_modules/.pnpm/safe-stable-stringify@2.5.0/node_modules/safe-stable-stringify/esm/wrapper.js
 var import__ = __toESM(require_safe_stable_stringify(), 1);
 var configure = import__.default.configure;
 var wrapper_default = import__.default;
@@ -9878,4 +9878,4 @@ export {
   defaultRegistry,
   createEngineFromEnv
 };
-//# sourceMappingURL=chunk-B7MLH3K6.js.map
+//# sourceMappingURL=chunk-4HRJQGVW.js.map