You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
Stage converts a Screenplay application's navigation topbar|sidebar regions to Scene's navigation model: the application's regions and logo from the layout, and each module's inherits/extends/overrides region, with item targets, slots, icons and sub-items. A document without regions serializes exactly as before. (part of #406)
Toolbar buttons become toolbar items that carry the slice, emphasis and icon the Scene engine reads, with the slice written as its qualified id.
Template assignments, own and blueprint with their version range, are carried as Scene template references, and the slice kinds of a scopes slice template travel in its metadata.
The render plan reports Scene's own structure, navigation and toolbar validation as findings - StructureInvalid, NavigationInvalid and ToolbarButtonInvalid - for example a navigation target that does not exist, or a toolbar button that names a State View slice. See the render plan findings.
Changed
Stage moves to Cratis.Scene 4.30.0 and Cratis.Screenplay 4.179.0, and the generated frontend pins the matching @cratis/scene.* packages.
The Billing sample demonstrates navigation regions and toolbar buttons.