@walkeros/core 4.7.1 → 4.7.2-next-1791213015481

package/CHANGELOG.md

@@ -1,5 +1,33 @@
 # @walkeros/core
 
+## 4.7.2-next-1791213015481
+
+### Patch Changes
+
+- 98398fe: An async mapping rule `condition` is now awaited, in rule order, so a
+  condition that resolves to `false` no longer matches. A condition that throws
+  is logged and counts as no match. New `isThenable` helper export.
+- 98398fe: MCP tool results are always an object: `mcpResult` answers a list as
+  `{ items }` and a bare value as `{ value }` instead of a bare or spread array,
+  and `project_manage list` always answers `{ projects }`.
+- ff23953: The MCP setup-mapping prompt, the MCP instructions, the schema
+  descriptions and the flow-complete example no longer claim that a mapping
+  rule's `consent` gates events. A rule's `consent` is not enforced yet; to
+  require consent for a destination, set `consent` in the destination's config.
+- 98398fe: A code-less transformer now runs its `config.mapping` (it wins over
+  the step-level `mapping`), and a flow bundle keeps a code-less transformer
+  whose only mapping or state sits in `config`. Init warns about every mapping
+  field that does nothing in a transformer, rules in array form included, about
+  a mapping next to `code` or `package`, which never runs, and about a
+  step-level `mapping` that `config.mapping` overrides; `validateFlowStructure`
+  reports the same warnings. New exports: `getTransformerMapping`,
+  `getTransformerMappingWarnings`.
+- 98398fe: `startFlow` now types each step by the package passed as `code`, so
+  settings, mapping rule settings and `env` keys autocomplete and an unknown
+  setting is a type error; steps without typed code stay as loose as before. The
+  Storybook addon no longer passes a `session` setting the browser source never
+  had.
+
 ## 4.7.1
 
 ### Patch Changes

package/dist/dev.d.mts

@@ -9160,10 +9160,11 @@ interface Config$2<T extends TypesGeneric$2 = Types$2> {
      * when a rule has `ignore: true`).
      *
      * At the transformer position, only event-mutating fields apply:
-     * `policy`, `mapping[].policy`, `mapping[].name`, `mapping[].ignore`,
-     * `mapping[].consent`, `include`. Vendor-payload fields (`data`,
-     * `mapping[].data`, `silent`) are ignored at this position with a
-     * one-time warning.
+     * `policy`, and per rule `condition`, `policy`, `name` and `ignore`.
+     * Everything else does nothing here and is named in a one-time init
+     * warning: `consent`, `include` and `data`, and per rule `consent`,
+     * `include`, `remove`, `batch`, `settings`, `extend`, `data` and
+     * `silent`. A `config.mapping` wins over the step-level `mapping`.
      */
     mapping?: Config$7;
 }
@@ -9234,8 +9235,9 @@ type Init$2<T extends TypesGeneric$2 = Types$2> = (context: Context$2<Types$2<Pa
 type InitTransformer<T extends TypesGeneric$2 = Types$2> = {
     /**
      * Initialization function. When omitted, the entry is a pass-through step:
-     * - If `mapping` is present, the collector synthesizes a mapping-only
-     *   push using `processEventMapping`.
+     * - If `mapping` or `config.mapping` is present, the collector
+     *   synthesizes a mapping-only push using `processEventMapping`. With
+     *   `code`, a mapping never runs (warned at init).
      * - Otherwise it's a named hop that only hosts a `before` / `next` /
      *   `cache` chain.
      *

package/dist/dev.d.ts

@@ -9160,10 +9160,11 @@ interface Config$2<T extends TypesGeneric$2 = Types$2> {
      * when a rule has `ignore: true`).
      *
      * At the transformer position, only event-mutating fields apply:
-     * `policy`, `mapping[].policy`, `mapping[].name`, `mapping[].ignore`,
-     * `mapping[].consent`, `include`. Vendor-payload fields (`data`,
-     * `mapping[].data`, `silent`) are ignored at this position with a
-     * one-time warning.
+     * `policy`, and per rule `condition`, `policy`, `name` and `ignore`.
+     * Everything else does nothing here and is named in a one-time init
+     * warning: `consent`, `include` and `data`, and per rule `consent`,
+     * `include`, `remove`, `batch`, `settings`, `extend`, `data` and
+     * `silent`. A `config.mapping` wins over the step-level `mapping`.
      */
     mapping?: Config$7;
 }
@@ -9234,8 +9235,9 @@ type Init$2<T extends TypesGeneric$2 = Types$2> = (context: Context$2<Types$2<Pa
 type InitTransformer<T extends TypesGeneric$2 = Types$2> = {
     /**
      * Initialization function. When omitted, the entry is a pass-through step:
-     * - If `mapping` is present, the collector synthesizes a mapping-only
-     *   push using `processEventMapping`.
+     * - If `mapping` or `config.mapping` is present, the collector
+     *   synthesizes a mapping-only push using `processEventMapping`. With
+     *   `code`, a mapping never runs (warned at init).
      * - Otherwise it's a named hop that only hosts a `before` / `next` /
      *   `cache` chain.
      *