|
| 1 | +--- |
| 2 | +'@objectstack/objectql': patch |
| 3 | +'@objectstack/service-automation': patch |
| 4 | +'@objectstack/runtime': patch |
| 5 | +--- |
| 6 | + |
| 7 | +Warnings, refusals and hints that cited a tracker number now say what was decided |
| 8 | + |
| 9 | +Clause-②: no |
| 10 | + |
| 11 | +Several runtime strings an author or operator reads sent the reader to an issue-tracker number for |
| 12 | +the reason behind them. Each now states that reason in the sentence itself: |
| 13 | + |
| 14 | +- `@objectstack/objectql`: the two data-event warnings. A write that names no single record publishes |
| 15 | + no per-record event rather than one with an empty `recordId`; a predicate (`multi: true`) write |
| 16 | + publishes its own `data.records.*` event carrying the affected-row count and nothing else, so a |
| 17 | + driver result that is not a count publishes no bulk event either. |
| 18 | +- `@objectstack/service-automation`: the warning for a pausing node type that never declares |
| 19 | + `resumeAuthority`, the generic-route resume refusal (its log line and its error text), and the |
| 20 | + refusal of a suspension from a type that declares `supportsPause: false`. An undeclared |
| 21 | + `resumeAuthority` resolves to `'service'` (fail-closed), so the generic resume route refuses those |
| 22 | + pauses; guessing `'any'` is how a raw resume once walked past an approval decision no service had |
| 23 | + recorded. |
| 24 | +- `@objectstack/runtime`: the endpoint step's `NOT_IMPLEMENTED` message and its two hints (the |
| 25 | + composed runtime always threads the policy context and the execution wiring, because execution is |
| 26 | + reachable only past the policy chain), and the endpoint mapping refusals (the publish gate rejects |
| 27 | + the same shapes, so a declaration that reaches the runtime check was stored without passing it). |
| 28 | + |
| 29 | +Text only: no error code, field name, status or behaviour changes. |
0 commit comments