@pipe0/base 1.0.0 → 1.0.2

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # @pipe0/ops
 
+## 1.0.2
+
+### Patch Changes
+
+- 1c4d867: Add rate limits
+- Updated dependencies [1c4d867]
+  - @pipe0/client@1.0.2
+
+## 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

@@ -23226,6 +23226,7 @@ declare const PipesResponseSchema: z.ZodObject<{
     processing: "processing";
     completed: "completed";
     failed: "failed";
+    canceled: "canceled";
     pending: "pending";
   }>;
 }, z.core.$strip>;
@@ -33350,6 +33351,12 @@ interface ConstantSuggestion {
   ownershipLevel: "organization" | "team" | "user";
   description: string | null;
   providerHint: string | null;
+  /**
+   * How the value is authored: `"value"` is a single line, `"text"` is
+   * multi-line prose. Surfaced so the picker can flag that a reference will
+   * expand to several lines — the `value` itself stays omitted.
+   */
+  format?: "value" | "text";
 }
 type GetSecretsArgs = {
   /**
@@ -56677,6 +56684,7 @@ declare const SearchResponseSchema: z$1.ZodObject<{
     processing: "processing";
     completed: "completed";
     failed: "failed";
+    canceled: "canceled";
     pending: "pending";
   }>;
   search_id: z$1.ZodEnum<{
@@ -62706,6 +62714,7 @@ declare const SearchesResponseSchema: z$1.ZodObject<{
     processing: "processing";
     completed: "completed";
     failed: "failed";
+    canceled: "canceled";
     pending: "pending";
   }>;
   results: z$1.ZodArray<z$1.ZodRecord<z$1.ZodString, z$1.ZodNullable<z$1.ZodObject<{
@@ -111850,7 +111859,7 @@ declare const PersonWorkemailWaterfall1Entry: {
   readonly keywords: readonly ["business email", "b2b", "corporate", "contact"];
   readonly docPath: string;
   readonly managedProviders: ["leadmagic", "prospeo", "amplemarket", "hunter", "icypeas", "findymail"];
-  readonly deprecatedProviders: ["icypeas"];
+  readonly deprecatedProviders: ["icypeas", "findymail"];
   readonly allowedUserConnectionProviders: ["leadmagic", "prospeo", "amplemarket", "hunter", "icypeas", "findymail"];
   readonly inputFieldMode: "static";
   readonly outputFieldMode: "static";
@@ -111942,8 +111951,6 @@ declare const PersonWorkemailWaterfall1Entry: {
         provider: "amplemarket";
       } | {
         provider: "hunter";
-      } | {
-        provider: "findymail";
       })[];
       readonly allow_catch_all_emails: true;
       readonly allow_risky_emails: true;
@@ -120008,13 +120015,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