@uipath/flow-tool 1.0.1 → 1.0.4

package/dist/utils/handle-expansion.d.ts

@@ -0,0 +1,50 @@
+/**
+ * Expand templated handle IDs declared on a node definition.
+ *
+ * A handle entry may set `repeat: "inputs.cases"` together with an `id` like
+ * `"case-{item.id}"`. The runtime, layout engine, and `node edge add` resolve
+ * these to one concrete handle per item in the referenced collection — so
+ * `flow validate` and any other consumer that checks handle IDs against edges
+ * must do the same expansion or it will reject every templated edge as an
+ * "undeclared source handle".
+ *
+ * The implementation matches the long-standing behavior in `tidy-service`'s
+ * port resolver — both call sites now share this helper.
+ *
+ * When the `repeat` path does not resolve to a literal array (e.g. the
+ * referenced field is itself an expression like `"=js:$vars.questions"`),
+ * expansion cannot enumerate concrete IDs at static-analysis time. In that
+ * case `expandHandleIds` returns the unexpanded template id as-is. Callers
+ * that need to match concrete edge ports against such templates should use
+ * `isTemplatedHandleId` + `portMatchesTemplate` to fall back to pattern
+ * matching, mirroring the regex-based approach used by `node edge add` and
+ * the canvas connection validator. Without this fallback `flow validate`
+ * would reject flows that the runtime accepts.
+ */
+export interface HandleEntry {
+    id: string;
+    repeat?: string;
+}
+export interface HandleExpansionNode {
+    inputs?: Record<string, unknown>;
+    [key: string]: unknown;
+}
+export declare function expandHandleIds(handle: HandleEntry, node: HandleExpansionNode): string[];
+/**
+ * True when `id` still carries an unsubstituted `{...}` placeholder — i.e.
+ * `expandHandleIds` could not enumerate concrete instances and returned the
+ * raw template (e.g. `"case-{item.id}"`).
+ */
+export declare function isTemplatedHandleId(id: string): boolean;
+/**
+ * Match a concrete edge port against a templated handle id by treating
+ * each `{...}` placeholder as a `.+` wildcard. Literal segments are escaped
+ * so regex metacharacters cannot leak through.
+ *
+ * Example: `portMatchesTemplate("case-q1", "case-{item.id}")` → `true`.
+ *
+ * Used by `flow validate` and `node edge add` to accept concrete edges
+ * pointing at templated handles when static expansion is not possible —
+ * e.g. when the `repeat` source is an expression evaluated at runtime.
+ */
+export declare function portMatchesTemplate(requestedPort: string, templateId: string): boolean;

package/dist/validation.d.ts

@@ -1,5 +1,5 @@
 /**
- * Side-effect-free public entry for the `uip flow validate` contribution
+ * Side-effect-free public entry for the `uip maestro flow validate` contribution
  * surface. Unlike the `tool.ts` entry (which registers CLI commands and
  * pulls in the solution-packager plugin chain), this module imports only
  * the validation service and its per-node-validator types, so downstream