@uipath/maestro-builder-sdk 6.60.0 → 6.61.0

package/README.md

@@ -105,20 +105,18 @@ write what you mean — an email address, the word `bot` — and `lookup()` reco
 the question. Now `check` has something to say:
 
 ```
-⚠ [LOOKUP_UNRESOLVED] Connector step "announce": input "channel" is an unresolved
-  lookup (profile.email="ada@example.com"). Compile does not make network calls, so
-  the value has to be resolved first:
-    npx flow-sdk registry prepare uipath-salesforce-slack --action send-message-to-user \
-      --resolve channel:profile.email=ada@example.com
-  Compile will fail until this is recorded.
-
-⚠ [LOOKUP_UNRESOLVED] … and the same for "send_as" (name="bot").
+✗ [LOOKUP_UNRESOLVED] connector uipath.connector.uipath-salesforce-slack.send-message-to-user:
+  inputs `channel` (profile.email="ada@example.com"), `send_as` (name="bot") are unresolved
+  lookups. Compile does not make network calls, so the values have to be resolved first:
+  npx flow-sdk registry prepare uipath-salesforce-slack --action send-message-to-user \
+    --resolve channel:profile.email=ada@example.com \
+    --resolve send_as:name=bot
 ```
 
-Warnings, not errors — the source pass still succeeds. It is `compile` that
-refuses, because resolving a lookup means asking the tenant and compile makes no
-network calls. That is what `prepare` is for: it is the one verb that does talk
-to the tenant. Run what `check` named, both fields at once:
+An error: `compile` refuses the step, because resolving a lookup means asking the
+tenant and compile makes no network calls, and `check` reports every refusal
+`compile` would raise. That is what `prepare` is for: it is the one verb that
+does talk to the tenant. Run what `check` named, both fields at once:
 
 ```bash
 uip maestro registry pull     # once per machine: the connector library

package/dist/api-index.md

@@ -37,7 +37,7 @@ could hand you spans for a version you do not have.
 
 ## `@uipath/maestro-builder-sdk`
 
-242 symbol(s). Import from `@uipath/maestro-builder-sdk`.
+243 symbol(s). Import from `@uipath/maestro-builder-sdk`.
 
 | Symbol | Kind | Declaration | Area | Summary |
 | --- | --- | --- | --- | --- |
@@ -192,7 +192,7 @@ could hand you spans for a version you do not have.
 | `LookupResolution` | interface | `dist/core/lookups.d.ts:165-174` | Generated descriptors | One recorded resolution, as `connectors-local/resolutions.json` stores it. |
 | `LookupResolutions` | type | `dist/core/lookups.d.ts:175-176` | Generated descriptors | Every recorded resolution, keyed by lookupKey. |
 | `LookupSpec` | interface | `dist/core/lookups.d.ts:11-36` | Generated descriptors | One lookup field's retrieval contract, generated from `reference`. |
-| `lookupSpecOf` | function | `dist/core/lookups.d.ts:221-228` | Generated descriptors | The LookupSpec for one field, or `undefined` when it earns no helper. |
+| `lookupSpecOf` | function | `dist/core/lookups.d.ts:234-241` | Generated descriptors | The LookupSpec for one field, or `undefined` when it earns no helper. |
 | `LookupStrategy` | type | `dist/core/lookups.d.ts:1-10` | Generated descriptors | How `prepare` should retrieve the collection, chosen from the metadata. |
 | `LookupToken` | interface | `dist/core/lookups.d.ts:37-52` | Generated descriptors | An unresolved lookup: what `.byEmail(…)` returns. |
 | `LoopOptions` | interface | `dist/flow-sdk.d.ts:522-546` | Option shapes | Loop-specific options. |
@@ -221,11 +221,11 @@ could hand you spans for a version you do not have.
 | `QueuePriority` | type | `dist/nodes/queue/flow/spec.d.ts:9-10` | Supporting types | The three priorities an Orchestrator queue item can carry. |
 | `ran` | function | `dist/core/expr.d.ts:95-141` | Expressions and types | Did this step run? |
 | `rawNode` | function | `dist/raw-node.d.ts:9-71` | Supporting types | Place a node this SDK has no factory for, carrying its definition verbatim (`uipath.exotic.thing@2.1` and the manifest… |
-| `RawReference` | type | `dist/core/lookups.d.ts:212-220` | Supporting types |  |
+| `RawReference` | type | `dist/core/lookups.d.ts:225-233` | Supporting types |  |
 | `RemoteA2aToolRef` | interface | `dist/core/actions.d.ts:471-491` | Supporting types | A remote A2A (agent-to-agent) endpoint the agent may delegate to. |
 | `resolvedEventValue` | function | `dist/core/lookups.d.ts:185-201` | Generated descriptors | resolvedValue for a token on an event's `where`. |
 | `resolvedValue` | function | `dist/core/lookups.d.ts:177-184` | Generated descriptors | The recorded id for a token, or `undefined`. |
-| `resolveEventWhere` | function | `dist/core/lookups.d.ts:229-246` | Generated descriptors | An event subscription's `where` with every lookup token swapped for the id `registry prepare --resolve` recorded, or a… |
+| `resolveEventWhere` | function | `dist/core/lookups.d.ts:242-259` | Generated descriptors | An event subscription's `where` with every lookup token swapped for the id `registry prepare --resolve` recorded, or a… |
 | `ReturnFieldType` | type | `dist/core/actions.d.ts:268-285` | Supporting types | A JSON-schema-ish type for one field of a step's declared `returns`. |
 | `ReturnOptions` | interface | `dist/flow-sdk.d.ts:480-521` | Option shapes | `.return(...)`-specific options. |
 | `rpaWorkflow` | function | `dist/nodes/process/flow/factories.d.ts:8-52` | Actions | Invoke a deployed RPA (robotic process automation) workflow — a classic UI-automation process, published to… |
@@ -272,6 +272,7 @@ could hand you spans for a version you do not have.
 | `TypeDesc` | type | `dist/core/expr.d.ts:385` | Supporting types |  |
 | `types` | const | `dist/core/expr.d.ts:369-384` | Expressions and types | Variable type descriptors (map to Flow variable `type` values). |
 | `unresolvedLookupMessage` | function | `dist/core/lookups.d.ts:202-211` | Generated descriptors | The message for a lookup nothing has resolved — the command that fixes it. |
+| `unresolvedLookupsMessage` | function | `dist/core/lookups.d.ts:212-224` | Generated descriptors | The message for every lookup one node still owes, with the ONE `prepare` that records them all (it takes every… |
 | `v` | function | `dist/core/expr.d.ts:29-41` | Expressions and types | Reference a flow variable or output by name → `$vars.<name>`. |
 | `VarDecl` | interface | `dist/flow-sdk.d.ts:61-73` | Supporting types | 7 field(s) |
 | `VarSpec` | interface | `dist/flow-sdk.d.ts:74-129` | Supporting types | The rich spelling of a variable declaration: pass it instead of a bare `types.*` descriptor wherever `.input()` /… |

package/dist/check-cli.js

@@ -5,7 +5,7 @@
  * Usage: node --experimental-strip-types check-cli.js <flow.ts | BaseName>
  * Prints diagnostics; exits non-zero if any errors.
  */
-import { reportDiagnostics } from './cli-result.js';
+import { diagnosticLine, reportDiagnostics } from './cli-result.js';
 import { defaultBindingsFile } from './workdir.js';
 import { resolveFlowFile, loadBuiltFlow } from './load.js';
 import { check } from './check.js';
@@ -17,14 +17,15 @@ import { ensureTypeScriptRuntime } from './node-runtime.js';
 const VALUE_FLAGS = new Set(['--library', '--bindings', '--connectors-local']);
 /**
  * Library lookups for the checks whose facts live in the connector corpus:
- * event parameters and measured list envelopes.
+ * event parameters and measured list envelopes, and the library `check`'s
+ * serializer run compiles with.
  *
  * Deliberately optional. `check` is the fast inner-loop rung and stays a pure
  * function of the built flow — with no library it simply cannot know whether an
- * empty `where` is correct, so it fails open (a warning, not an error). Given a
- * library, `compile` and `check` make the same call with the facts in hand.
- * `--library` and `--connectors-local` mirror compile-cli's flags and defaults,
- * through the same `openCliLibrary`.
+ * empty `where` is correct, or lower a connector step, so it fails open (a
+ * warning, or nothing). Given a library, `compile` and `check` make the same
+ * call with the facts in hand. `--library` and `--connectors-local` mirror
+ * compile-cli's flags and defaults, through the same `openCliLibrary`.
  */
 function checkOpts(argv) {
     // The default bindings.json (workdir.ts), exactly as compile-cli finds it — so the
@@ -53,7 +54,7 @@ export async function run(argv) {
         return 0;
     }
     for (const d of diags)
-        console.log(`${d.level === 'error' ? '✗' : '⚠'} [${d.code}] ${d.message}${d.suggestion ? ` (did you mean "${d.suggestion}"?)` : ''}`);
+        console.log(diagnosticLine(d));
     const errors = diags.filter((d) => d.level === 'error').length;
     console.log(`\n${errors} error(s), ${diags.length - errors} warning(s)`);
     return errors ? 1 : 0;

package/dist/check.d.ts

@@ -1,3 +1,4 @@
+import type { Library } from './core/library.js';
 import type { BuiltFlow } from './flow-sdk.js';
 import { type EventCheckOpts } from './core/event-checks.js';
 export type { EventParamFields } from './core/event-checks.js';
@@ -34,6 +35,16 @@ export interface CheckOpts extends ConnectorCheckOpts, EventCheckOpts {
      * whether it grants an error port is then the same answer in both rungs.
      */
     connectorDefinition?: (connector: string, operation: string, version?: string, object?: string) => unknown;
+    /**
+     * The connector library `compile` serializes with. `check` runs the
+     * serializer in collect mode, with this library and `bindings`, to report
+     * every refusal `compile` would raise from the one place each rule lives;
+     * `flowCheckOpts` passes the library `compile` opens. Without one, a step only
+     * a library can lower is not judged (check fails open, as its library rules do).
+     */
+    library?: Library;
+    /** `false` skips the serializer pass, for a caller that compiles the flow itself (`merge`). */
+    serializer?: false;
 }
 export declare function check(built: BuiltFlow, opts?: CheckOpts): Diagnostic[];
 /**