@jarenjs/flow 0.72.0 → 0.72.3

package/README.md

@@ -139,7 +139,7 @@ const dag = compileDag({
   nodes: {
     rows:   { kind: 'input' },
     adults: { kind: 'query',
-      query: { $for: { r: '$[*]' }, $where: { $ge: ['$r.age', 18] }, $return: '$r' } },
+      query: [{ $for: { r: '$[*]' }, $where: { $ge: ['$r.age', 18] }, $return: '$r' }] },
     view:   { kind: 'jslt',
       stylesheet: [{ match: '$', body: ['ul', {},
         [{ $for: { p: '$[*]' }, $return: ['li', {}, '$p.name'] }]] }] },
@@ -155,6 +155,10 @@ const dag = compileDag({
 await dag.run(people);   // ['ul', {}, [['li', {}, 'ada'], …]] — a vnode, as JSON
 ```
 
+The query's outer array keeps `adults` an array for zero, one or many
+rows. Without it, the engine's one-result sequence becomes that row;
+the next node's `$[*]` would iterate its members instead of rows.
+
 Cycles, port rules and the exactly-one-output rule are **compile-time**
 rejections (JF0xxx with `docPath`); a `task` node's handler is resolved
 at compile too, and called as `handler({ with, input }, signal)` with

package/docs/FLOW-FORMAT.md

@@ -261,7 +261,7 @@ extending it is a format revision, not an option.
   "nodes": {
     "rows": { "kind": "input" },
     "adults": { "kind": "query",
-      "query": { "$for": { "r": "$[*]" }, "$where": { "$ge": ["$r.age", 18] }, "$return": "$r" } },
+      "query": [{ "$for": { "r": "$[*]" }, "$where": { "$ge": ["$r.age", 18] }, "$return": "$r" }] },
     "names": { "kind": "jslt",
       "stylesheet": [{ "match": "$", "body": ["ul", {},
         [{ "$for": { "p": "$[*]" }, "$return": ["li", {}, "$p.name"] }]] }] },
@@ -312,7 +312,15 @@ A node's `$` is decided by its inbound edges:
 
 A delivery whose `select` yields the empty sequence delivers `null`; a
 `query`/`jslt` node whose own result is empty likewise yields `null` —
-`undefined` is not a JSON value and never flows through a graph.
+`undefined` is not a JSON value and never flows through a graph. The
+query engine's singleton rule also applies: one result is that value,
+while two or more results become an array. To deliver an array for every
+cardinality, wrap the query in an array constructor, as `adults.query`
+does above. Its downstream `$[*]` therefore always iterates rows. The
+stylesheet also collects its `li` children in an explicit array: zero,
+one and two adults yield respectively `["ul", {}, []]`,
+`["ul", {}, [["li", {}, "ada"]]]`, and
+`["ul", {}, [["li", {}, "ada"], ["li", {}, "lin"]]]` for those names.
 Values pass **by reference**: nodes and hosts MUST NOT mutate what
 they receive.
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@jarenjs/flow",
   "private": false,
-  "version": "0.72.0",
+  "version": "0.72.3",
   "type": "module",
   "main": "./src/index.js",
   "types": "./dist/types/index.d.ts",
@@ -49,7 +49,7 @@
     "prepack": "npm run build:types"
   },
   "dependencies": {
-    "@jarenjs/core": "^0.72.0",
-    "@jarenjs/json": "^0.72.0"
+    "@jarenjs/core": "^0.72.3",
+    "@jarenjs/json": "^0.72.3"
   }
 }

package/src/dag.js

@@ -466,6 +466,8 @@ export function compileDag(doc, options) {
         loaded = await checkpoint.load(runId);
       }
       catch (err) {
+        if (signal !== undefined && onAbort !== null)
+          signal.removeEventListener('abort', onAbort);
         const cause = asError(err);
         throw new FlowRuntimeError('JF2009',
           `the checkpoint store failed to load run '${runId}': ${cause.message}`,