@xeplr/actions 1.4.4 → 1.4.5

package/README.md

@@ -191,7 +191,7 @@ await runAction({ name: 'data-operation', input: {
   sort: '-late',
   format: true, title: 'Overdue'
 } })
-// → { rows, count, html, text }
+// → { rows, count, columns, html, text }
 ```
 
 **Rows and a rendering, both.** `rows` and `count` are always there; `html`
@@ -199,6 +199,8 @@ and `text` only when `format` is on, because building a table for ten
 thousand rows nobody renders is work done and stored on every run. Neither is
 privileged — the next step binds whichever it wants.
 
+**`columns` says the order and the headings** (`[{ key, header }]`, the visible ones), in `export-table`'s column shape, so a workflow writes `document: { columns: "{steps.overdue.output.columns}" }`. Why: a step's output is stored as JSONB, which reorders a row's keys (shortest first), so the next step cannot read the column order off a row. A file exported without it came out as `late, amount, invoice, customer`.
+
 **`count` is the point of the step as often as `rows` is**: it is what lets
 the step after it branch on *nothing to report* instead of sending an empty
 email.

package/lib/builtins/data-operation.js

@@ -106,7 +106,9 @@ module.exports = {
     { name: 'rows', type: 'array', description: 'What is left, with the columns asked for.' },
     { name: 'count', type: 'number', description: 'How many rows — so the next step can branch on none.' },
     { name: 'html', type: 'string', description: 'A table of the visible columns. Only when `format` is on.' },
-    { name: 'text', type: 'string', description: 'The same, as plain text, for a mail client that refuses HTML.' }
+    { name: 'text', type: 'string', description: 'The same, as plain text, for a mail client that refuses HTML.' },
+    { name: 'columns', type: 'array', description: 'The visible columns, in order: [{ key, header }]. Give it to export-table ' +
+      'as document.columns: a step\'s stored output does not keep its fields in order.' }
   ],
 
   // The same call every action gets from runAction: { input, system }. It
@@ -183,7 +185,15 @@ module.exports = {
       });
     }
 
-    var result = { rows: rows, count: rows.length };
+    // THE ORDER AND THE HEADINGS, said out loud. A step's output is stored
+    // as JSONB, which reorders an object's keys (shortest first), so the next
+    // step cannot read the column order off a row. This is export-table's
+    // column shape, so it is handed over as it is.
+    var result = {
+      rows: rows,
+      count: rows.length,
+      columns: computed.filter(function(c) { return !c.hidden; }).map(function(c) { return { key: c.name, header: c.label }; })
+    };
 
     if (input.format) {
       // THE VISIBLE COLUMNS ONLY. A column kept for the next step but not

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xeplr/actions",
-  "version": "1.4.4",
+  "version": "1.4.5",
   "description": "Named-action registry with typed inputs and safe invocation — plus built-in actions for HTTP, DB, files, email, spawn",
   "main": "index.js",
   "scripts": {