@particle-academy/fancy-flow 0.53.0 → 0.55.0

package/dist/{ConfigFieldRenderer-Bc9Txnql.d.cts → HumanPrompt-CPl-Spmp.d.cts}

@@ -89,4 +89,78 @@ type ConfigFieldRendererProps = {
  */
 declare function ConfigFieldRenderer({ field, value, onChange, id, renderCredentialField, renderDocumentField, fieldRenderers, graph, nodeId, }: ConfigFieldRendererProps): react.JSX.Element | null;
 
-export { type ConfigFieldRenderFn as C, type ConfigFieldRenderContext as a, ConfigFieldRenderer as b, type ConfigFieldRendererProps as c };
+/**
+ * The field vocabulary a `user_input` node declares, and the normalizer that
+ * turns whatever was actually written into something renderable.
+ *
+ * ## Why this is a separate module from `HumanPrompt.tsx`
+ *
+ * `src/registry/builtin.ts` needs `humanFieldType` for the `user_input` kind's
+ * `outputShape`, and `builtin.ts` is in the import graph of the `/engine`
+ * entry — the one `tests/core-nodes.test.ts` guards as React-free so a queue
+ * worker or a CLI can register kinds without dragging React in. Importing the
+ * modal's `.tsx` from there put a React module on that path and left the guard
+ * standing only because treeshaking happened to drop it.
+ *
+ * Pure functions over plain data, in a `.ts` file, so the headless path cannot
+ * regress on a future edit to the component.
+ */
+/**
+ * The control a field renders as, after {@link humanInputFields} has resolved
+ * whatever the author, a peer runtime or an agent actually wrote.
+ *
+ * These are the CANONICAL names. The vocabulary an author may write is wider —
+ * see {@link HUMAN_FIELD_TYPE_ALIASES} — because a `fields` array arrives from
+ * three places (the config panel, a hand-written workflow JSON, and the PHP /
+ * Python runtimes) and each has its own habits for spelling "boolean".
+ */
+type HumanFieldType = "text" | "textarea" | "number" | "select" | "switch" | "date" | "datetime" | "time" | "email" | "url" | "tel" | "password";
+/** One choice in a `select` field, after normalization. */
+type HumanFieldOption = {
+    value: string;
+    label: string;
+};
+/** A field the input modal renders. Mirrors a `user_input` `fields` row. */
+type HumanField = {
+    key: string;
+    label?: string;
+    type?: HumanFieldType;
+    required?: boolean;
+    placeholder?: string;
+    options?: HumanFieldOption[];
+    default?: unknown;
+};
+
+/** What a host renderer is handed for one field. */
+type HumanFieldRenderContext = {
+    field: HumanField;
+    /** The id the field's `<label>` points at — put it on your control. */
+    id: string;
+    value: unknown;
+    onChange: (v: unknown) => void;
+    /** Present only on the first field; attach it so the modal autofocuses. */
+    autoFocusRef?: React.RefObject<HTMLElement | null>;
+};
+/**
+ * Render one field, or return `null` to decline it.
+ *
+ * `null` means "not mine" and falls through to the built-in control. That is
+ * what makes a PARTIAL map safe to spread: a host handing over someone else's
+ * renderers does not silently lose every type that map does not cover.
+ */
+type HumanFieldRenderFn = (ctx: HumanFieldRenderContext) => ReactNode | null;
+/**
+ * Host overrides for pause-form controls, keyed by CANONICAL field type
+ * (`"switch"`, not `"boolean"` — aliases are normalised before the lookup, so
+ * one entry covers every spelling of that type).
+ *
+ * The built-ins are deliberately native `--ff-*`-themed elements rather than
+ * react-fancy primitives: react-fancy is an OPTIONAL peer and this modal ships
+ * in the main entry, so importing it here would break a standalone install and
+ * bypass the token layer a host themes `.ff-editor` with. This seam is how a
+ * host that HAS react-fancy gets Fancy controls anyway —
+ * `@particle-academy/fancy-flow/fields/react-fancy` exports a ready map.
+ */
+type HumanFieldRenderers = Partial<Record<HumanFieldType, HumanFieldRenderFn>>;
+
+export { type ConfigFieldRenderFn as C, type HumanFieldRenderers as H, type ConfigFieldRenderContext as a, ConfigFieldRenderer as b, type ConfigFieldRendererProps as c };

package/dist/{ConfigFieldRenderer-Bt3RGT7Z.d.ts → HumanPrompt-DlJSFi3F.d.ts}

@@ -89,4 +89,78 @@ type ConfigFieldRendererProps = {
  */
 declare function ConfigFieldRenderer({ field, value, onChange, id, renderCredentialField, renderDocumentField, fieldRenderers, graph, nodeId, }: ConfigFieldRendererProps): react.JSX.Element | null;
 
-export { type ConfigFieldRenderFn as C, type ConfigFieldRenderContext as a, ConfigFieldRenderer as b, type ConfigFieldRendererProps as c };
+/**
+ * The field vocabulary a `user_input` node declares, and the normalizer that
+ * turns whatever was actually written into something renderable.
+ *
+ * ## Why this is a separate module from `HumanPrompt.tsx`
+ *
+ * `src/registry/builtin.ts` needs `humanFieldType` for the `user_input` kind's
+ * `outputShape`, and `builtin.ts` is in the import graph of the `/engine`
+ * entry — the one `tests/core-nodes.test.ts` guards as React-free so a queue
+ * worker or a CLI can register kinds without dragging React in. Importing the
+ * modal's `.tsx` from there put a React module on that path and left the guard
+ * standing only because treeshaking happened to drop it.
+ *
+ * Pure functions over plain data, in a `.ts` file, so the headless path cannot
+ * regress on a future edit to the component.
+ */
+/**
+ * The control a field renders as, after {@link humanInputFields} has resolved
+ * whatever the author, a peer runtime or an agent actually wrote.
+ *
+ * These are the CANONICAL names. The vocabulary an author may write is wider —
+ * see {@link HUMAN_FIELD_TYPE_ALIASES} — because a `fields` array arrives from
+ * three places (the config panel, a hand-written workflow JSON, and the PHP /
+ * Python runtimes) and each has its own habits for spelling "boolean".
+ */
+type HumanFieldType = "text" | "textarea" | "number" | "select" | "switch" | "date" | "datetime" | "time" | "email" | "url" | "tel" | "password";
+/** One choice in a `select` field, after normalization. */
+type HumanFieldOption = {
+    value: string;
+    label: string;
+};
+/** A field the input modal renders. Mirrors a `user_input` `fields` row. */
+type HumanField = {
+    key: string;
+    label?: string;
+    type?: HumanFieldType;
+    required?: boolean;
+    placeholder?: string;
+    options?: HumanFieldOption[];
+    default?: unknown;
+};
+
+/** What a host renderer is handed for one field. */
+type HumanFieldRenderContext = {
+    field: HumanField;
+    /** The id the field's `<label>` points at — put it on your control. */
+    id: string;
+    value: unknown;
+    onChange: (v: unknown) => void;
+    /** Present only on the first field; attach it so the modal autofocuses. */
+    autoFocusRef?: React.RefObject<HTMLElement | null>;
+};
+/**
+ * Render one field, or return `null` to decline it.
+ *
+ * `null` means "not mine" and falls through to the built-in control. That is
+ * what makes a PARTIAL map safe to spread: a host handing over someone else's
+ * renderers does not silently lose every type that map does not cover.
+ */
+type HumanFieldRenderFn = (ctx: HumanFieldRenderContext) => ReactNode | null;
+/**
+ * Host overrides for pause-form controls, keyed by CANONICAL field type
+ * (`"switch"`, not `"boolean"` — aliases are normalised before the lookup, so
+ * one entry covers every spelling of that type).
+ *
+ * The built-ins are deliberately native `--ff-*`-themed elements rather than
+ * react-fancy primitives: react-fancy is an OPTIONAL peer and this modal ships
+ * in the main entry, so importing it here would break a standalone install and
+ * bypass the token layer a host themes `.ff-editor` with. This seam is how a
+ * host that HAS react-fancy gets Fancy controls anyway —
+ * `@particle-academy/fancy-flow/fields/react-fancy` exports a ready map.
+ */
+type HumanFieldRenderers = Partial<Record<HumanFieldType, HumanFieldRenderFn>>;
+
+export { type ConfigFieldRenderFn as C, type HumanFieldRenderers as H, type ConfigFieldRenderContext as a, ConfigFieldRenderer as b, type ConfigFieldRendererProps as c };

package/dist/{chunk-CIBW5ATA.js → chunk-22OJOD4X.js}

@@ -9454,7 +9454,7 @@ function resolveWorkflowProps(declared, passed) {
 // src/runtime/run-flow.ts
 async function runFlow(graph, executors, onEvent = () => {
 }, options = {}) {
-  const { signal, initialInputs = {}, timeoutMs, depth = 0, resumeOutputs = {} } = options;
+  const { signal, initialInputs = {}, timeoutMs, depth = 0, resumeOutputs = {}, entryNodes } = options;
   const run = options.run === void 0 ? void 0 : RunIdentity.from(options.run);
   const outputs = {};
   const portValues = /* @__PURE__ */ new Map();
@@ -9493,6 +9493,10 @@ async function runFlow(graph, executors, onEvent = () => {
         continue;
       }
       const incoming = incomingByNode.get(node.id) ?? [];
+      if (incoming.length === 0 && entryNodes !== void 0 && !entryNodes.includes(node.id)) {
+        onEvent({ type: "node-status", nodeId: node.id, status: "idle", text: "skipped" });
+        continue;
+      }
       if (incoming.length > 0) {
         const anyActive = incoming.some((e) => portValues.has(`${e.source}:${e.sourceHandle ?? "out"}`));
         if (!anyActive) {
@@ -10848,5 +10852,5 @@ function LaneNodeInner(props) {
 var LaneNode = memo(LaneNodeInner);
 
 export { BUILTIN_KINDS, Background, BackgroundVariant, Controls, DEFAULT_MAX_DEPTH, FlowEditorProvider, Handle, LaneNode, MiniMap, NodeResizer, NodeToolbar, NoteNode, Position, ReactFlowProvider, RunIdentity, ViewportPortal, addEdge2 as addEdge, applyEdgeChanges, applyNodeChanges, categoryAccent, clearNodeKindOverrides, declaredRoutes, defaultConfigFor, ensureBuiltinKinds, escapeSegment, getNodeKind, humanInputFields, index, kindIds, listNodeKinds, llmRouterExecutor, nodeConfig, onNodeKindsChanged, overrideNodeKind, reconnectEdge2 as reconnectEdge, registerBuiltinKinds, registerNodeKind, resolveFallbackPort, resolveKindId, resolveNodePorts, resolvePortSpec, runFlow, subflowExecutor, subflowMode, subflowPorts, useFlowEditor, useFlowEditorOptional, useReactFlow, validateConfig };
-//# sourceMappingURL=chunk-CIBW5ATA.js.map
-//# sourceMappingURL=chunk-CIBW5ATA.js.map
+//# sourceMappingURL=chunk-22OJOD4X.js.map
+//# sourceMappingURL=chunk-22OJOD4X.js.map