Skip to content

Release v4.226.0

Choose a tag to compare

@github-actions github-actions released this 19 Oct 02:21
59dc11d

Changed

  • A command can append to several event sources: a production's for may name any required scalar command property, so one accepted command appends an event to the order and another to the product (#859)
  • A specification can pin the generated values a reaction-invoked command takes with given generated <Command>.<property> = <value>, so a reaction that creates a purchase order with a generated id is specified, not left unsupported (#858)
  • A capture over events carries a list across a context boundary whole (lines = $.lines) or fans out one private event per element with children lines identified by sku, and nested scopes into an object (#857)
  • The golden, canonical corpus, contract probes, conformance syntax vector and documentation carry them; several event sources and pinned values select ESM v30 (decision 0098)
  • The Acme Commerce sample uses all eight admissions (decimals, products, concept conversion, application toolbar buttons, published events, several event sources, pinned generated values, list fan-out) and its workarounds are gone: 173 of 173 specifications pass with no unsupported and no warnings

AI corpus: Cratis/AI#806