bem-ai-sdk 0.24.0 → 0.26.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -539,31 +539,38 @@ export namespace FunctionVersion {
539
539
 
540
540
  export interface EnrichFunctionVersion {
541
541
  /**
542
- * Configuration for enrich function with semantic search steps.
542
+ * Configuration for an enrich function.
543
543
  *
544
544
  * **How Enrich Functions Work:**
545
545
  *
546
- * Enrich functions use semantic search to augment JSON data with relevant
547
- * information from collections. They take JSON input (typically from a transform
548
- * function), extract specified fields, perform vector-based semantic search
549
- * against collections, and inject the results back into the data.
546
+ * Enrich functions augment JSON input with data from external sources. They take
547
+ * JSON input (typically from a previous function), extract specified fields, fetch
548
+ * or search for matching data, and inject the results back into the JSON.
549
+ *
550
+ * **Data Sources:**
551
+ *
552
+ * - **Collections** (`source: "collection"`): Vector/keyword search against a BEM
553
+ * collection. Best for semantic matching against pre-indexed documents.
554
+ * - **Endpoints** (`source: "endpoint"`): HTTP call to any user-provided REST API.
555
+ * Best for looking up live data from CRMs, ERPs, or other external systems.
556
+ * Optionally uses LLM agent reasoning to rank candidates returned by the
557
+ * endpoint.
550
558
  *
551
559
  * **Input Requirements:**
552
560
  *
553
- * - Must receive JSON input (typically uploaded to S3 from a previous function)
554
- * - Can be chained after transform or other functions that produce JSON output
561
+ * - Must receive JSON input (typically from a previous function's output)
555
562
  *
556
563
  * **Example Use Cases:**
557
564
  *
558
- * - Match product descriptions to SKU codes from a product catalog
559
- * - Enrich customer data with account information
560
- * - Link order line items to inventory records
565
+ * - Match product descriptions to SKU codes from a product catalog collection
566
+ * - Enrich customer data with account details from a CRM endpoint
567
+ * - Use LLM agent reasoning to fuzzy-match line item descriptions to catalog
568
+ * products
561
569
  *
562
570
  * **Configuration:**
563
571
  *
564
- * - Define one or more enrichment steps
565
- * - Each step extracts values, searches a collection, and injects results
566
- * - Steps are executed sequentially
572
+ * - Define named endpoints (for endpoint-source steps)
573
+ * - Define one or more enrichment steps; steps are executed sequentially
567
574
  */
568
575
  config: FunctionsAPI.EnrichConfig;
569
576
 
@@ -703,6 +710,13 @@ export namespace FunctionVersion {
703
710
  */
704
711
  displayName?: string;
705
712
 
713
+ /**
714
+ * Cross-cutting toggles for Parse functions. Mirrors the `extraConfig` surface on
715
+ * Extract / Join — separated from `parseConfig` so the per-call Parse output shape
716
+ * stays distinct from operator-level execution flags.
717
+ */
718
+ extraConfig?: ParseFunctionVersion.ExtraConfig;
719
+
706
720
  /**
707
721
  * Per-version configuration for a Parse function.
708
722
  *
@@ -722,6 +736,26 @@ export namespace FunctionVersion {
722
736
  */
723
737
  usedInWorkflows?: Array<FunctionsAPI.WorkflowUsageInfo>;
724
738
  }
739
+
740
+ export namespace ParseFunctionVersion {
741
+ /**
742
+ * Cross-cutting toggles for Parse functions. Mirrors the `extraConfig` surface on
743
+ * Extract / Join — separated from `parseConfig` so the per-call Parse output shape
744
+ * stays distinct from operator-level execution flags.
745
+ */
746
+ export interface ExtraConfig {
747
+ /**
748
+ * When true, return per-section and per-entity-mention coordinates in the parse
749
+ * event's `fieldBoundingBoxes` map (same shape as Extract: JSON Pointer key →
750
+ * array of `{page, left, top, width, height}` with coordinates normalized to [0,
751
+ * 1]). Keys are `/sections/{N}` and `/entities/{N}/occurrences/{M}` into the parse
752
+ * output. Only applies to the open-ended discovery path (no `schema`) and to
753
+ * vision input types. Bedrock-backed parse functions silently return an empty map
754
+ * (no native bbox support). Defaults to false.
755
+ */
756
+ enableBoundingBoxes?: boolean;
757
+ }
758
+ }
725
759
  }
726
760
 
727
761
  export interface ListFunctionVersionsResponse {
package/src/version.ts CHANGED
@@ -1 +1 @@
1
- export const VERSION = '0.24.0'; // x-release-please-version
1
+ export const VERSION = '0.26.0'; // x-release-please-version
package/version.d.mts CHANGED
@@ -1,2 +1,2 @@
1
- export declare const VERSION = "0.24.0";
1
+ export declare const VERSION = "0.26.0";
2
2
  //# sourceMappingURL=version.d.mts.map
package/version.d.ts CHANGED
@@ -1,2 +1,2 @@
1
- export declare const VERSION = "0.24.0";
1
+ export declare const VERSION = "0.26.0";
2
2
  //# sourceMappingURL=version.d.ts.map
package/version.js CHANGED
@@ -1,5 +1,5 @@
1
1
  "use strict";
2
2
  Object.defineProperty(exports, "__esModule", { value: true });
3
3
  exports.VERSION = void 0;
4
- exports.VERSION = '0.24.0'; // x-release-please-version
4
+ exports.VERSION = '0.26.0'; // x-release-please-version
5
5
  //# sourceMappingURL=version.js.map
package/version.mjs CHANGED
@@ -1,2 +1,2 @@
1
- export const VERSION = '0.24.0'; // x-release-please-version
1
+ export const VERSION = '0.26.0'; // x-release-please-version
2
2
  //# sourceMappingURL=version.mjs.map