@pipe0/base 1.0.0 → 1.0.1

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @pipe0/ops
 
+## 1.0.1
+
+### Patch Changes
+
+- 75012eb: Fix template syntax
+- Updated dependencies [75012eb]
+  - @pipe0/client@1.0.1
+
 ## 1.0.0
 
 ### Major Changes

package/dist/index.d.mts

@@ -120008,13 +120008,22 @@ declare function parseLiquidTemplate(template: string): _$liquidjs.Template[];
  * resulting input refs into a single `Requirement`. A field referenced as
  * required in any template wins; otherwise it stays optional.
  *
- * `expectedType` and `expectedFormat` mirror today's `pipesTaggedTextInput`
- * defaults (`string` / `text`) — they're metadata only, not enforced. Per the
- * plan, type compatibility is resolved at evaluation time, not at parse time.
+ * `expectedType` is metadata — a fallback for when the column isn't in the lazy
+ * context. Type compatibility is resolved at evaluation time, not at parse time.
+ *
+ * There is deliberately no expected FORMAT. A template ref names an arbitrary
+ * user-chosen column, so the leaf has no format requirement — same as every
+ * other arbitrary-column leaf (`formula:run@1`, `bucket:*@1`, `row:append:sheet@1`).
+ * This used to default to `"text"`, copied from `pipesTaggedTextInput`'s form
+ * metadata, where it is a display hint. On a requirement leaf it is not a hint:
+ * the runner cleans every value through it, so `"text"` silently stringified
+ * whatever it received. That turned a boolean column into `"true"` before the
+ * Liquid engine ever saw it, and since liquid `==` is strict identity,
+ * `{% if flag == true %}` could never match. Values now arrive raw and the
+ * engine decides how to present them (see `outputEscape` in engine.ts).
  */
 declare function buildInputRequirementFromTemplates(templates: Array<string | null | undefined>, opts?: {
   expectedType?: RecordFieldType;
-  expectedFormat?: RecordFieldFormat;
 }): Requirement;
 /**
  * Run the analyzer over every templated config field and return the deduped