@enrichlayer/el-linear 1.15.0 → 1.16.0

package/dist/commands/comments.js

@@ -196,7 +196,28 @@ async function handleUpdateComment(commentId, options, command) {
     else {
         input.body = body;
     }
-    const result = await graphQLService.rawRequest(UPDATE_COMMENT_MUTATION, { id: commentId, input });
+    let result;
+    try {
+        result = await graphQLService.rawRequest(UPDATE_COMMENT_MUTATION, { id: commentId, input });
+    }
+    catch (err) {
+        // Same defense-in-depth fallback as `handleCreateComment` above: when
+        // Linear rejects `bodyData` (schema drift, unsupported node, validator
+        // quirk), retry the mutation with raw markdown `body` so the update
+        // goes through even if our prosemirror converter has fallen behind a
+        // schema change. The asymmetry between create and update used to mean
+        // any future drift would silently break updates while creates kept
+        // working — DEV-4261 closes that gap. Two call sites is the floor for
+        // extraction; copy-then-refactor on the third per the repo convention.
+        const msg = err instanceof Error ? err.message : String(err);
+        if (input.bodyData && BODY_DATA_ERROR_RE.test(msg)) {
+            const fallbackInput = { body };
+            result = await graphQLService.rawRequest(UPDATE_COMMENT_MUTATION, { id: commentId, input: fallbackInput });
+        }
+        else {
+            throw err;
+        }
+    }
     const mutation = result.commentUpdate;
     if (!mutation.success || !mutation.comment) {
         throw new Error("Failed to update comment");

package/dist/output.d.ts

@@ -0,0 +1,82 @@
+/**
+ * Public output utilities — secondary entry point for cross-CLI reuse.
+ *
+ * Other Enrich Layer CLIs (el-slack, el-sheets, el-audit, el-git,
+ * el-elasticsearch — currently in the `tools` monorepo) should depend on
+ * `@enrichlayer/el-linear` and import this module to share the same
+ * `--jq` / `--fields` / `--raw` / `--format summary` behavior and the
+ * canonical `{ data, meta }` envelope shape. DEV-3799.
+ *
+ * Why this exists rather than a separate package: linctl is the OSS
+ * canonical source of these patterns (DEV-3619, DEV-3637, DEV-3798); it
+ * already publishes to npm and ships compiled JS in `dist/`. Treating it
+ * as the host of the shared utilities means there is exactly one
+ * implementation, exactly one set of tests, and exactly one place where
+ * the envelope contract is documented. Tools-repo CLIs pick it up via
+ * `pnpm add @enrichlayer/el-linear` and `import { outputSuccess, ... }
+ * from "@enrichlayer/el-linear/output"`.
+ *
+ * Stable API — semver-tracked. Anything re-exported here MUST stay
+ * backwards-compatible across minor releases. Adding exports is fine;
+ * renaming or removing them is a breaking change.
+ *
+ * # Wiring (consumer recipe)
+ *
+ * Each CLI's `main.ts` registers four global options and a `preAction`
+ * hook to read them into the shared state:
+ *
+ * ```ts
+ * import { Command } from "commander";
+ * import {
+ *   setRawMode, setJqFilter, setFieldsFilter, setOutputFormat,
+ * } from "@enrichlayer/el-linear/output";
+ *
+ * const program = new Command()
+ *   .option("--raw", "strip { data, meta } wrapper from list output")
+ *   .option("--jq <filter>", "apply a jq filter to the JSON output")
+ *   .option("--fields <fields>", "comma-separated field allow-list")
+ *   .option("--format <fmt>", "json | summary", "json");
+ *
+ * program.hook("preAction", (_thisCommand, actionCommand) => {
+ *   const o = actionCommand.optsWithGlobals();
+ *   if (o.raw) setRawMode(true);
+ *   if (o.jq) setJqFilter(o.jq);
+ *   if (o.fields) {
+ *     setFieldsFilter(o.fields.split(",").map((s: string) => s.trim()));
+ *   }
+ *   setOutputFormat(o.format === "summary" ? "summary" : "json");
+ * });
+ * ```
+ *
+ * Then in each subcommand handler emit results via `outputList(data)` /
+ * `outputSingle(data)` / `outputSuccess(payload)`, wrap async actions in
+ * `handleAsyncCommand`, and buffer informational messages via
+ * `outputWarning`. The shared state in this module takes care of `--jq`,
+ * `--fields`, `--raw`, and summary rendering uniformly.
+ *
+ * Adapt the option names and flags to your CLI's existing conventions —
+ * the contract is the four setter calls (`setRawMode`, `setJqFilter`,
+ * `setFieldsFilter`, `setOutputFormat`), not the literal `--jq` /
+ * `--fields` / `--raw` / `--format` names. A CLI that already exposes
+ * `--json` / `--summary` shorthands can keep them as long as the
+ * preAction hook ends up calling the same setters with equivalent values.
+ *
+ * # What is NOT exported
+ *
+ * - `--format summary` dispatch tables are linctl-specific (Linear
+ *   resources). Other CLIs that want summary rendering should either
+ *   ship `--format json` only or register their own per-command summary
+ *   path that does not consume this module's `setOutputFormat("summary")`.
+ * - `outputError` is intentionally internal — it calls `process.exit(1)`
+ *   directly. Consumers funnel errors through `handleAsyncCommand`, which
+ *   in turn calls `outputError`. Don't re-export the bare function; the
+ *   wrapper is the contract.
+ * - Token-sanitization (`sanitizeForLog`) is internal to the error path.
+ *   Consumers that route errors through `handleAsyncCommand` automatically
+ *   get token redaction on the error path — no separate redactor needed
+ *   for that case. If a consumer wants sanitization for something OTHER
+ *   than thrown errors (e.g. a custom debug log), it should pull a small
+ *   redactor of its own; coupling token redaction to the output layer
+ *   would make this API surface stickier than it needs to be.
+ */
+export { type CliListEnvelope, getOutputFormat, handleAsyncCommand, type ListExtraMeta, type ListMeta, outputList, outputSingle, outputSuccess, outputWarning, resetWarnings, setFieldsFilter, setJqFilter, setOutputFormat, setRawMode, warnIfTruncated, } from "./utils/output.js";

package/dist/output.js

@@ -0,0 +1,82 @@
+/**
+ * Public output utilities — secondary entry point for cross-CLI reuse.
+ *
+ * Other Enrich Layer CLIs (el-slack, el-sheets, el-audit, el-git,
+ * el-elasticsearch — currently in the `tools` monorepo) should depend on
+ * `@enrichlayer/el-linear` and import this module to share the same
+ * `--jq` / `--fields` / `--raw` / `--format summary` behavior and the
+ * canonical `{ data, meta }` envelope shape. DEV-3799.
+ *
+ * Why this exists rather than a separate package: linctl is the OSS
+ * canonical source of these patterns (DEV-3619, DEV-3637, DEV-3798); it
+ * already publishes to npm and ships compiled JS in `dist/`. Treating it
+ * as the host of the shared utilities means there is exactly one
+ * implementation, exactly one set of tests, and exactly one place where
+ * the envelope contract is documented. Tools-repo CLIs pick it up via
+ * `pnpm add @enrichlayer/el-linear` and `import { outputSuccess, ... }
+ * from "@enrichlayer/el-linear/output"`.
+ *
+ * Stable API — semver-tracked. Anything re-exported here MUST stay
+ * backwards-compatible across minor releases. Adding exports is fine;
+ * renaming or removing them is a breaking change.
+ *
+ * # Wiring (consumer recipe)
+ *
+ * Each CLI's `main.ts` registers four global options and a `preAction`
+ * hook to read them into the shared state:
+ *
+ * ```ts
+ * import { Command } from "commander";
+ * import {
+ *   setRawMode, setJqFilter, setFieldsFilter, setOutputFormat,
+ * } from "@enrichlayer/el-linear/output";
+ *
+ * const program = new Command()
+ *   .option("--raw", "strip { data, meta } wrapper from list output")
+ *   .option("--jq <filter>", "apply a jq filter to the JSON output")
+ *   .option("--fields <fields>", "comma-separated field allow-list")
+ *   .option("--format <fmt>", "json | summary", "json");
+ *
+ * program.hook("preAction", (_thisCommand, actionCommand) => {
+ *   const o = actionCommand.optsWithGlobals();
+ *   if (o.raw) setRawMode(true);
+ *   if (o.jq) setJqFilter(o.jq);
+ *   if (o.fields) {
+ *     setFieldsFilter(o.fields.split(",").map((s: string) => s.trim()));
+ *   }
+ *   setOutputFormat(o.format === "summary" ? "summary" : "json");
+ * });
+ * ```
+ *
+ * Then in each subcommand handler emit results via `outputList(data)` /
+ * `outputSingle(data)` / `outputSuccess(payload)`, wrap async actions in
+ * `handleAsyncCommand`, and buffer informational messages via
+ * `outputWarning`. The shared state in this module takes care of `--jq`,
+ * `--fields`, `--raw`, and summary rendering uniformly.
+ *
+ * Adapt the option names and flags to your CLI's existing conventions —
+ * the contract is the four setter calls (`setRawMode`, `setJqFilter`,
+ * `setFieldsFilter`, `setOutputFormat`), not the literal `--jq` /
+ * `--fields` / `--raw` / `--format` names. A CLI that already exposes
+ * `--json` / `--summary` shorthands can keep them as long as the
+ * preAction hook ends up calling the same setters with equivalent values.
+ *
+ * # What is NOT exported
+ *
+ * - `--format summary` dispatch tables are linctl-specific (Linear
+ *   resources). Other CLIs that want summary rendering should either
+ *   ship `--format json` only or register their own per-command summary
+ *   path that does not consume this module's `setOutputFormat("summary")`.
+ * - `outputError` is intentionally internal — it calls `process.exit(1)`
+ *   directly. Consumers funnel errors through `handleAsyncCommand`, which
+ *   in turn calls `outputError`. Don't re-export the bare function; the
+ *   wrapper is the contract.
+ * - Token-sanitization (`sanitizeForLog`) is internal to the error path.
+ *   Consumers that route errors through `handleAsyncCommand` automatically
+ *   get token redaction on the error path — no separate redactor needed
+ *   for that case. If a consumer wants sanitization for something OTHER
+ *   than thrown errors (e.g. a custom debug log), it should pull a small
+ *   redactor of its own; coupling token redaction to the output layer
+ *   would make this API surface stickier than it needs to be.
+ */
+export { getOutputFormat, handleAsyncCommand, outputList, outputSingle, outputSuccess, outputWarning, resetWarnings, setFieldsFilter, setJqFilter, setOutputFormat, setRawMode, warnIfTruncated, } from "./utils/output.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@enrichlayer/el-linear",
-  "version": "1.15.0",
+  "version": "1.16.0",
   "description": "A pragmatic CLI for Linear.app — deterministic team/label/member resolution, structured issue validation, configurable term enforcement, and a GraphQL escape hatch.",
   "main": "dist/main.js",
   "types": "dist/main.d.ts",
@@ -9,6 +9,11 @@
     ".": {
       "types": "./dist/main.d.ts",
       "import": "./dist/main.js"
+    },
+    "./output": {
+      "types": "./dist/output.d.ts",
+      "import": "./dist/output.js",
+      "default": "./dist/output.js"
     }
   },
   "sideEffects": false,