Repository navigation
Release v4.23.0
Scene gains a read-only description of an application's modules, features and slices (with each slice's kind) that navigation, toolbar and template-applicability rules can query. Closes part of the spec epic #96.
Added
ApplicationStructure,ModuleNode,FeatureNode,SliceNodeandSliceKind(StateChange,StateView,Automation) inCratis.Scene.Model.Structureand@cratis/scene.model, mirrored inscene-model-shape.json. The structure is a reference input supplied by the host (Stage's converter, Studio); it is not persisted in a scene document.ApplicationStructureIndexinCratis.Scene.Engine.Structureandengine/structure:findModule,findFeature,firstFeature/firstFeatureId,findSlice,kindOf,findFeaturesByNameand the diagnosticsstructureDuplicateIdandstructureAmbiguousName. Pure, no DOM.application-structure-fixtures.json(qualified lookup, nested features, first feature, module without features, unknown/wrongly typed ids, same-named features in different modules, duplicate ids, ambiguous names) asserted by bothEngine.Specs/for_ApplicationStructureIndexandengine/for_applicationStructureIndex.- The documentation page
blueprints/application-structure.mdexplains the input and who supplies it.
Part of #97