Repository navigation
Release v6.6.0
A model can now name the journeys that run through it, and trace any value both ways from wherever it appears.
Added
storyline <Name> ["<title>"]names an ordered path through a model, such as a user journey. Each step names a module, feature, slice, command, event, read model, query, screen or reaction, with an optional note. Renaming or moving an element rewrites the steps that name it, a step that names nothing warns withPLAY0942, and storylines never change the executable model. See Storylines. (#1189)- The MCP tool
list-storylineslists every storyline with its steps resolved to the elements they name; storylines are edited withpropose-astandpropose-source. trace-lineagestarts from a command, event or read-model property or a screen field, and tracesupstream,downstreamorboth. Downstream follows the value through productions, projections and reaction invocations to the queries and screens that show it. (#1190)screenplay lineage <address> [<folder>]prints the same trace as text or JSON, with--direction, and exits 1 when the trace has breaks. See Trace a value's lineage.