Repository navigation
Release v5.0.0
Stage now compiles Screenplay 6 and renders with Scene 5: slots with roles and routing, outlets of every kind, placement, and hooks that run their command directly. A routed slot is part of the address, so a selected item, a chosen tab and filter values survive a reload or a shared link. This is a major version.
Added
- Slots carry their role and whether they are routed, and outlets of actions, filters, tabs, stats and navigation reach Scene with their defaults, refinements and contributions. (#1007)
fits,opens dialog|drawer|in slot,for item|for screen,enabled when,confirm,choose from query … show …pickers andshow <Screen> by <param> from <element>.selectionare translated into Scene.- A routed slot is part of the address: opening a screen in it, the chosen tab of the slot that owns the tabs, and a routed page's filter values survive a reload or a shared link. Back and forward move through routed slot changes and tabs; dialogs, drawers and panels never change the address.
- A
runshook issues its command directly with the resolved inputs, asks itsconfirmfirst, and refreshes the page's queries.
Changed
- Breaking: Stage compiles Screenplay 6 and renders with Scene 5. Migrate models with
screenplay migrate <model root> --from 5 --to 6; the old outlet and navigation region forms are refused with a message naming the migration. - Breaking: a screen toolbar becomes a Scene
core:outletItemselement of outlet buttons instead ofcore:toolbar. A placement of primary, secondary or quiet becomes the button's emphasis, and other presentation values are reported asSTAGE-SCENE-TOOLBAR-002. Consumers that read the scene JSON or depend on frozen scene bytes must update. - Stage builds on Scene 5.1.0, Chronicle 19.142.0, Arc 22.176.0 and Screenplay generation 0.20.0. An icon-only toolbar item becomes an icon-only outlet button that keeps its title as its accessible name.