@enrichlayer/el-linear 1.33.0 → 1.34.0

package/dist/commands/issues.js

@@ -1042,8 +1042,30 @@ export function setupIssuesCommands(program) {
     const issues = program
         .command("issues")
         .alias("issue")
-        .description("Issue operations");
-    issues.action(() => issues.help());
+        .description("Issue operations")
+        .argument("[issueId...]", "issue ID(s) to read when no subcommand is given — shorthand for `issues read`")
+        .option("--body", "Print the issue's full description as raw markdown text — no JSON " +
+        "envelope, single-issue only. Exits non-zero if the issue has no " +
+        "description. The whole-body sibling of --field; mutually exclusive " +
+        "with --field / --sections / --with.")
+        .option("--field <name>", 'Extract a single named section from the issue description (e.g. "Done when"). ' +
+        "Matches H2/H3 headers and bold pseudo-headers case-insensitively. " +
+        "Outputs the section text only — no JSON envelope. Single-issue only.")
+        .option("--sections <names>", 'Extract multiple named description sections in one call (comma-separated, e.g. "Done when,Out of scope"). ' +
+        "Single-issue only. Returns a JSON envelope { identifier, sections: { name -> text|null } }; missing sections appear as null + a _warnings entry. " +
+        "Sibling of --field (singular). Named --sections rather than --fields because the program already has a global --fields for output-key filtering.")
+        .option("--with <names>", "Comma-separated opt-in includes. Each value fetches an extra " +
+        'block of data and adds it to the JSON envelope. Currently supported: "relations" ' +
+        "(adds an array of cross-issue relations under a top-level `relations` key).")
+        .addHelpText("after", "\nNo-subcommand shorthand: `el-linear issue DEV-123` behaves like `issues read DEV-123`, " +
+        "including its options (--body, --field, --sections, --with).");
+    issues.action(handleAsyncCommand((issueIds = [], options, command) => {
+        if (issueIds.length === 0) {
+            issues.help();
+            return Promise.resolve();
+        }
+        return readIssues(issueIds, options, command);
+    }));
     // DEV-4480: `issues tree <ID>` lives in its own file because the
     // recursive query builder + ASCII formatter belong together and are
     // substantial enough to warrant the split.

package/dist/utils/formatters/summary.d.ts

@@ -42,6 +42,15 @@ export declare function formatLabelList(labels: unknown[]): string;
  * the row falls back to the stored direction.
  */
 export declare function formatRelationList(relations: unknown[], sourceRef?: string): string;
+/**
+ * Table render for `issues related <id>` — the `{ data: RelatedIssueEntry[] }`
+ * envelope where each entry is `{ type, direction, issue }`. Distinct from
+ * `formatRelationList` (the `issues relate` mutation echo, `{ type, issue,
+ * relatedIssue }` shape): this is the read-path listing of ALL of an issue's
+ * relations, so direction, state, and assignee are surfaced per row instead
+ * of collapsing to a single source-oriented type/target/title line.
+ */
+export declare function formatIssueRelationList(relations: unknown[]): string;
 export declare function formatUserSummary(user: Record<string, unknown>): string;
 export declare function formatUserList(users: unknown[]): string;
 export declare function formatDocumentSummary(doc: Record<string, unknown>): string;
@@ -59,7 +68,7 @@ export declare function formatSearchResultList(results: unknown[]): string;
  * the full payload. Lists fall back to a simple bulleted list.
  */
 export declare function formatGenericSummary(value: unknown): string;
-export type ResourceKind = "issue" | "issue-list" | "project" | "project-list" | "comment" | "comment-list" | "cycle" | "cycle-list" | "milestone" | "milestone-list" | "team-list" | "label-list" | "user" | "user-list" | "document" | "document-list" | "template" | "template-list" | "attachment-list" | "release" | "release-list" | "search-result-list" | "relation-list" | "empty-list" | "generic";
+export type ResourceKind = "issue" | "issue-list" | "project" | "project-list" | "comment" | "comment-list" | "cycle" | "cycle-list" | "milestone" | "milestone-list" | "team-list" | "label-list" | "user" | "user-list" | "document" | "document-list" | "template" | "template-list" | "attachment-list" | "release" | "release-list" | "search-result-list" | "relation-list" | "issue-relation-list" | "empty-list" | "generic";
 /**
  * Heuristic — used by the central `outputSuccess` path which doesn't know
  * which command produced the payload. Looks at the shape of the data to

package/dist/utils/formatters/summary.js

@@ -749,6 +749,42 @@ export function formatRelationList(relations, sourceRef = "—") {
         },
     ], { emptyText: "(no relations)", itemNoun: "relation" });
 }
+/**
+ * Table render for `issues related <id>` — the `{ data: RelatedIssueEntry[] }`
+ * envelope where each entry is `{ type, direction, issue }`. Distinct from
+ * `formatRelationList` (the `issues relate` mutation echo, `{ type, issue,
+ * relatedIssue }` shape): this is the read-path listing of ALL of an issue's
+ * relations, so direction, state, and assignee are surfaced per row instead
+ * of collapsing to a single source-oriented type/target/title line.
+ */
+export function formatIssueRelationList(relations) {
+    const rows = relations.map((raw) => asObj(raw) ?? {});
+    return renderTable(rows, [
+        { header: "RELATION", minWidth: 8, extract: (r) => s(r.type) },
+        { header: "DIRECTION", minWidth: 9, extract: (r) => s(r.direction) },
+        {
+            header: "ID",
+            minWidth: 2,
+            extract: (r) => s(asObj(r.issue)?.identifier),
+        },
+        {
+            header: "STATE",
+            minWidth: 5,
+            extract: (r) => getName(asObj(r.issue)?.state),
+        },
+        {
+            header: "ASSIGNEE",
+            minWidth: 8,
+            extract: (r) => getName(asObj(r.issue)?.assignee),
+        },
+        {
+            header: "TITLE",
+            minWidth: 5,
+            maxWidth: TITLE_TRUNC,
+            extract: (r) => s(asObj(r.issue)?.title),
+        },
+    ], { emptyText: "(no issue relations)", itemNoun: "relation" });
+}
 // ── users ──────────────────────────────────────────────────────
 export function formatUserSummary(user) {
     const name = s(user.name);
@@ -1032,6 +1068,10 @@ function inferListKind(items) {
     // identifier/title, so this must precede the issue-list check below.
     if ("relatedIssue" in sample && "issue" in sample && "type" in sample)
         return "relation-list";
+    // `issues related <id>` rows ({ type, direction, issue }) — the read-path
+    // listing, distinct from the `relatedIssue`-shaped mutation echo above.
+    if ("direction" in sample && "issue" in sample && "type" in sample)
+        return "issue-relation-list";
     if ("identifier" in sample && "title" in sample) {
         // could be issue or search result
         if ("type" in sample && !("templateData" in sample)) {
@@ -1154,6 +1194,8 @@ export function dispatch(kind, payload, fields) {
             return formatSearchResultList(list ?? []);
         case "relation-list":
             return formatRelationList(list ?? [], s(asObj(obj?.meta)?.source));
+        case "issue-relation-list":
+            return formatIssueRelationList(list ?? []);
         case "empty-list":
             return "(no results)";
         case "generic":

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@enrichlayer/el-linear",
-  "version": "1.33.0",
+  "version": "1.34.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",