Skip to content

Release v6.6.0

Choose a tag to compare

@github-actions github-actions released this 08 Nov 23:45
4e2df31

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 with PLAY0942, and storylines never change the executable model. See Storylines. (#1189)
  • The MCP tool list-storylines lists every storyline with its steps resolved to the elements they name; storylines are edited with propose-ast and propose-source.
  • trace-lineage starts from a command, event or read-model property or a screen field, and traces upstream, downstream or both. 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.