@pipelex/mthds-form 0.3.0 → 0.5.0

package/dist/core/gate.js

@@ -0,0 +1,12 @@
+export { apiInputsFromSchemaData, buildRunInputsSchema, gateRunInputs, prepareRunInputs, validateRunInputs } from '../chunk-IM2AHWBR.js';
+import '../chunk-LBFZXYCY.js';
+import '../chunk-GCXV76WU.js';
+import '../chunk-PM55AHRO.js';
+import '../chunk-VTPUDBSJ.js';
+import '../chunk-GKV77RAS.js';
+import '../chunk-YEVVR6FE.js';
+import '../chunk-OD3VYXUY.js';
+import '../chunk-XYQ7NXQZ.js';
+import '../chunk-V3OV2XQT.js';
+//# sourceMappingURL=gate.js.map
+//# sourceMappingURL=gate.js.map

package/dist/core/gate.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":[],"names":[],"mappings":"","file":"gate.js"}

package/dist/core/gating-fields.d.ts

@@ -0,0 +1,38 @@
+import { PipeInputContract } from 'mthds/protocol';
+import { RunField } from './descriptor.js';
+import './contracts.js';
+
+/**
+ * The gate's own field tree - structural, schema-derived, and private.
+ *
+ * `gateRunInputs` re-applies the Run button's emptiness rule with
+ * `mustBeFilled`/`fieldFilled`, which read a `RunField` tree. The RENDER tree
+ * is built from the wire input-form descriptor - but the gate must not require
+ * that artifact: the descriptor is a presentation view, and the workspace
+ * doctrine is that a machine consumer never needs it to validate a payload -
+ * `json_schema` keeps that job. A server holds contracts; it may never have
+ * asked for the view.
+ *
+ * So the gate walks the contract's `json_schema` into the MINIMAL tree the
+ * emptiness predicates read: `object` nodes with their required children,
+ * `list` nodes with their declared bounds, and opaque leaves. This is not a
+ * revival of the deleted heuristics - it reads exactly the keywords ajv itself
+ * enforces (`type`, `properties`, `required`, `items`, `minItems`, `maxItems`)
+ * and decides nothing about what a field IS. No kind here ever reaches a
+ * renderer: the tree exists for one call inside `gateRunInputs` and is not
+ * exported from the package.
+ *
+ * Agreement with the browser's readiness (which runs over the render tree) is
+ * held by construction - both trees take required children and list bounds
+ * from the same model the engine derived both artifacts from - and asserted in
+ * `gate-agreement.test.ts`, which runs both sides over one table.
+ */
+
+/**
+ * The tree `gateRunInputs`' emptiness re-check runs over, one node per input,
+ * with `gating` stamped from the contract - the same `inputMustBeFilled` the
+ * Run button's `required` list is built from.
+ */
+declare function gatingFieldsFromInputs(inputs: Record<string, PipeInputContract>): RunField[];
+
+export { gatingFieldsFromInputs };

package/dist/core/gating-fields.js

@@ -0,0 +1,6 @@
+export { gatingFieldsFromInputs } from '../chunk-YEVVR6FE.js';
+import '../chunk-OD3VYXUY.js';
+import '../chunk-XYQ7NXQZ.js';
+import '../chunk-V3OV2XQT.js';
+//# sourceMappingURL=gating-fields.js.map
+//# sourceMappingURL=gating-fields.js.map

package/dist/core/gating-fields.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":[],"names":[],"mappings":"","file":"gating-fields.js"}