@cratis/scene.blueprint.components 0.1.0

package/dist/cjs/templates/editorTemplates.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"editorTemplates.js","sources":["../../../templates/editorTemplates.ts"],"sourcesContent":["// Copyright (c) Cratis. All rights reserved.\n// Licensed under the MIT license. See LICENSE file in the project root for full license information.\n\nimport { ScreenTemplate, WidthSizeClass } from '@cratis/scene.model';\nimport { SlotName, TemplateSlotName, column, row, slotLeaf } from '@cratis/scene.blueprint.default';\nimport { filterPanel, objectContentEditor, objectNavigationalBar, schemaEditor, timeMachine } from './editorElements';\nimport { arcPageHeader, errorBoundary, page, toolbar, toolbarButton, toolbarSeparator } from './elements';\nimport { SampleBindingName } from './SampleBindingName';\n\n/**\n * The two inspection pages: one for a type's shape, one for an instance's content.\n *\n * These are the templates to open first when looking at this blueprint, because they are the two that\n * render completely with nothing registered. The schema editor, the document editor, the navigational bar\n * and the time machine all read their content out of the property bag rather than from a query, so a\n * preview of either page is a working page rather than a page of placeholders.\n *\n * That is not a trick to make a demo look better. It is the honest shape of the library: most of\n * `@cratis/components` is Arc-bound and needs a host, and a meaningful part of it is not. A blueprint built\n * on it should make both halves visible.\n */\n\n/**\n * The schema editor page: an event type's shape, edited as a typed property tree.\n *\n * Its header names no binding, and that is correct rather than an omission. A schema is design-time\n * metadata about an event type, not a read model anyone queries, so there is nothing for the header to be\n * bound to - and the header says `No binding` instead of implying a wiring step that does not exist. It is\n * the one page in this package where the unbound state is the finished state.\n *\n * `canEdit` is paired with `canNotEditReason` deliberately: in an event-sourced application a stored event\n * type's schema is very often deliberately locked, and saying why in the same place is what stops that\n * from reading as a bug.\n */\nexport const schemaEditorPageTemplate: ScreenTemplate = {\n    name: 'SchemaEditorPage',\n    fitsSlot: SlotName.Content,\n    slots: [{ name: TemplateSlotName.Header }, { name: TemplateSlotName.Toolbar }, { name: TemplateSlotName.Body }],\n    arrangement: {\n        root: column([slotLeaf(TemplateSlotName.Header), slotLeaf(TemplateSlotName.Toolbar), slotLeaf(TemplateSlotName.Body, { grow: 1 })], 16),\n    },\n    content: {\n        [TemplateSlotName.Header]: [\n            arcPageHeader('schema-header', {\n                title: 'InvoiceRegistered',\n                subtitle: 'The shape of the event, and what a new generation would be allowed to change',\n                section: 'Event types',\n            }),\n        ],\n        [TemplateSlotName.Toolbar]: [\n            toolbar('schema-toolbar', [\n                toolbarButton('schema-edit', 'Edit the schema', 'pi pi-pencil', 'Edit'),\n                toolbarButton('schema-generation', 'Start a new generation', 'pi pi-clone', 'New generation'),\n                toolbarSeparator('schema-separator'),\n                toolbarButton('schema-download', 'Download as JSON Schema', 'pi pi-download'),\n            ]),\n        ],\n        [TemplateSlotName.Body]: [\n            page('schema-body', 'InvoiceRegistered', [schemaEditor('schema-editor', 'InvoiceRegistered', true)]),\n        ],\n    },\n    displayName: 'Schema editor page',\n    description: \"An event type's schema edited as a typed property tree, with the actions that evolve it.\",\n};\n\n/**\n * The object editor page: one document, its trail, and its history beside it.\n *\n * Bound to `InvoiceById`, because that is what a real page like this is: you arrive with an id, the query\n * fetches the record, and the editor renders it against its schema. The editors themselves take their\n * content from the property bag, so the page is fully legible before the query is wired - and the header\n * still says which query it is waiting for.\n *\n * The document is wrapped in an `errorBoundary` and the history is not, which is the decision this element\n * exists to let a template make. A malformed document should cost the document region; it should not take\n * the trail and the timeline down with it, and the timeline is the thing you would reach for to find out\n * *when* the document became malformed.\n */\nexport const objectEditorPageTemplate: ScreenTemplate = {\n    name: 'ObjectEditorPage',\n    fitsSlot: SlotName.Content,\n    slots: [\n        { name: TemplateSlotName.Header },\n        { name: TemplateSlotName.Toolbar },\n        { name: TemplateSlotName.Body },\n        { name: TemplateSlotName.SidePanel },\n    ],\n    arrangement: {\n        root: column([\n            slotLeaf(TemplateSlotName.Header),\n            slotLeaf(TemplateSlotName.Toolbar),\n            row([slotLeaf(TemplateSlotName.Body, { grow: 2 }), slotLeaf(TemplateSlotName.SidePanel, { grow: 1 })], 16),\n        ]),\n        overrides: [\n            {\n                width: WidthSizeClass.Compact,\n                root: column(\n                    [\n                        slotLeaf(TemplateSlotName.Header),\n                        slotLeaf(TemplateSlotName.Toolbar),\n                        slotLeaf(TemplateSlotName.Body),\n                        slotLeaf(TemplateSlotName.SidePanel),\n                    ],\n                    16,\n                ),\n            },\n        ],\n    },\n    content: {\n        [TemplateSlotName.Header]: [\n            arcPageHeader('object-header', {\n                title: 'INV-2043',\n                subtitle: 'The document as it stands, and every version it has been',\n                section: 'Billing',\n                query: SampleBindingName.InvoiceById,\n            }),\n        ],\n        [TemplateSlotName.Toolbar]: [objectNavigationalBar('object-trail'), filterPanel('object-filters', 'Filters')],\n        [TemplateSlotName.Body]: [\n            errorBoundary('object-guard', [page('object-body', 'Document', [objectContentEditor('object-editor', true)])]),\n        ],\n        [TemplateSlotName.SidePanel]: [page('object-history', 'History', [timeMachine('object-time-machine')])],\n    },\n    displayName: 'Object editor page',\n    description: 'One document edited against its schema, with its navigation trail and its version history.',\n};\n\n/** The two editor-shaped templates. */\nexport const editorTemplates: ScreenTemplate[] = [schemaEditorPageTemplate, objectEditorPageTemplate];\n"],"names":["schemaEditorPageTemplate","name","fitsSlot","SlotName","Content","slots","TemplateSlotName","Header","Toolbar","Body","arrangement","root","column","slotLeaf","grow","content","arcPageHeader","title","subtitle","section","toolbar","toolbarButton","toolbarSeparator","page","schemaEditor","displayName","description","objectEditorPageTemplate","SidePanel","row","overrides","width","WidthSizeClass","Compact","query","SampleBindingName","InvoiceById","objectNavigationalBar","filterPanel","errorBoundary","objectContentEditor","timeMachine","editorTemplates"],"mappings":";;;;;;;;AAAA;AACA;AAQA;;;;;;;;;;;;;;;;;;;;;;UAyBaA,wBAAAA,GAA2C;IACpDC,IAAAA,EAAM,kBAAA;AACNC,IAAAA,QAAAA,EAAUC,iCAASC,OAAO;IAC1BC,KAAAA,EAAO;AAAC,QAAA;AAAEJ,YAAAA,IAAAA,EAAMK,yCAAiBC;AAAO,SAAA;AAAG,QAAA;AAAEN,YAAAA,IAAAA,EAAMK,yCAAiBE;AAAQ,SAAA;AAAG,QAAA;AAAEP,YAAAA,IAAAA,EAAMK,yCAAiBG;AAAK;AAAE,KAAA;IAC/GC,WAAAA,EAAa;AACTC,QAAAA,IAAAA,EAAMC,8BAAAA,CAAO;AAACC,YAAAA,gCAAAA,CAASP,yCAAiBC,MAAM,CAAA;AAAGM,YAAAA,gCAAAA,CAASP,yCAAiBE,OAAO,CAAA;YAAGK,gCAAAA,CAASP,wCAAAA,CAAiBG,IAAI,EAAE;gBAAEK,IAAAA,EAAM;AAAE,aAAA;SAAG,EAAE,EAAA;AACxI,KAAA;IACAC,OAAAA,EAAS;QACL,CAACT,wCAAAA,CAAiBC,MAAM,GAAG;AACvBS,YAAAA,sBAAAA,CAAc,eAAA,EAAiB;gBAC3BC,KAAAA,EAAO,mBAAA;gBACPC,QAAAA,EAAU,8EAAA;gBACVC,OAAAA,EAAS;AACb,aAAA;AACH,SAAA;QACD,CAACb,wCAAAA,CAAiBE,OAAO,GAAG;AACxBY,YAAAA,gBAAAA,CAAQ,gBAAA,EAAkB;gBACtBC,sBAAAA,CAAc,aAAA,EAAe,mBAAmB,cAAA,EAAgB,MAAA,CAAA;gBAChEA,sBAAAA,CAAc,mBAAA,EAAqB,0BAA0B,aAAA,EAAe,gBAAA,CAAA;gBAC5EC,yBAAAA,CAAiB,kBAAA,CAAA;AACjBD,gBAAAA,sBAAAA,CAAc,mBAAmB,yBAAA,EAA2B,gBAAA;AAC/D,aAAA;AACJ,SAAA;QACD,CAACf,wCAAAA,CAAiBG,IAAI,GAAG;AACrBc,YAAAA,aAAAA,CAAK,eAAe,mBAAA,EAAqB;AAACC,gBAAAA,2BAAAA,CAAa,iBAAiB,mBAAA,EAAqB,IAAA;AAAM,aAAA;AACtG;AACL,KAAA;IACAC,WAAAA,EAAa,oBAAA;IACbC,WAAAA,EAAa;AACjB;AAEA;;;;;;;;;;;;UAaaC,wBAAAA,GAA2C;IACpD1B,IAAAA,EAAM,kBAAA;AACNC,IAAAA,QAAAA,EAAUC,iCAASC,OAAO;IAC1BC,KAAAA,EAAO;AACH,QAAA;AAAEJ,YAAAA,IAAAA,EAAMK,yCAAiBC;AAAO,SAAA;AAChC,QAAA;AAAEN,YAAAA,IAAAA,EAAMK,yCAAiBE;AAAQ,SAAA;AACjC,QAAA;AAAEP,YAAAA,IAAAA,EAAMK,yCAAiBG;AAAK,SAAA;AAC9B,QAAA;AAAER,YAAAA,IAAAA,EAAMK,yCAAiBsB;AAAU;AACtC,KAAA;IACDlB,WAAAA,EAAa;AACTC,QAAAA,IAAAA,EAAMC,8BAAAA,CAAO;AACTC,YAAAA,gCAAAA,CAASP,yCAAiBC,MAAM,CAAA;AAChCM,YAAAA,gCAAAA,CAASP,yCAAiBE,OAAO,CAAA;YACjCqB,2BAAAA,CAAI;gBAAChB,gCAAAA,CAASP,wCAAAA,CAAiBG,IAAI,EAAE;oBAAEK,IAAAA,EAAM;AAAE,iBAAA,CAAA;gBAAID,gCAAAA,CAASP,wCAAAA,CAAiBsB,SAAS,EAAE;oBAAEd,IAAAA,EAAM;AAAE,iBAAA;aAAG,EAAE,EAAA;AAC1G,SAAA,CAAA;QACDgB,SAAAA,EAAW;AACP,YAAA;AACIC,gBAAAA,KAAAA,EAAOC,2BAAeC,OAAO;AAC7BtB,gBAAAA,IAAAA,EAAMC,8BAAAA,CACF;AACIC,oBAAAA,gCAAAA,CAASP,yCAAiBC,MAAM,CAAA;AAChCM,oBAAAA,gCAAAA,CAASP,yCAAiBE,OAAO,CAAA;AACjCK,oBAAAA,gCAAAA,CAASP,yCAAiBG,IAAI,CAAA;AAC9BI,oBAAAA,gCAAAA,CAASP,yCAAiBsB,SAAS;iBACtC,EACD,EAAA;AAER;AACH;AACL,KAAA;IACAb,OAAAA,EAAS;QACL,CAACT,wCAAAA,CAAiBC,MAAM,GAAG;AACvBS,YAAAA,sBAAAA,CAAc,eAAA,EAAiB;gBAC3BC,KAAAA,EAAO,UAAA;gBACPC,QAAAA,EAAU,0DAAA;gBACVC,OAAAA,EAAS,SAAA;AACTe,gBAAAA,KAAAA,EAAOC,oCAAkBC;AAC7B,aAAA;AACH,SAAA;QACD,CAAC9B,wCAAAA,CAAiBE,OAAO,GAAG;YAAC6B,oCAAAA,CAAsB,cAAA,CAAA;AAAiBC,YAAAA,0BAAAA,CAAY,gBAAA,EAAkB,SAAA;AAAW,SAAA;QAC7G,CAAChC,wCAAAA,CAAiBG,IAAI,GAAG;AACrB8B,YAAAA,sBAAAA,CAAc,cAAA,EAAgB;AAAChB,gBAAAA,aAAAA,CAAK,eAAe,UAAA,EAAY;AAACiB,oBAAAA,kCAAAA,CAAoB,eAAA,EAAiB,IAAA;AAAM,iBAAA;AAAE,aAAA;AAChH,SAAA;QACD,CAAClC,wCAAAA,CAAiBsB,SAAS,GAAG;AAACL,YAAAA,aAAAA,CAAK,kBAAkB,SAAA,EAAW;gBAACkB,0BAAAA,CAAY,qBAAA;AAAuB,aAAA;AAAE;AAC3G,KAAA;IACAhB,WAAAA,EAAa,oBAAA;IACbC,WAAAA,EAAa;AACjB;AAEA,wCACO,MAAMgB,eAAAA,GAAoC;AAAC1C,IAAAA,wBAAAA;AAA0B2B,IAAAA;;;;;;;"}

package/dist/cjs/templates/elements.js

@@ -0,0 +1,101 @@
+'use strict';
+
+var scene_blueprint_default = require('@cratis/scene.blueprint.default');
+var ComponentName = require('../ComponentName.js');
+var CompositeName = require('../CompositeName.js');
+
+// Copyright (c) Cratis. All rights reserved.
+// Licensed under the MIT license. See LICENSE file in the project root for full license information.
+/**
+ * The page furniture every template in this package repeats.
+ *
+ * `externalComponent` is imported from the default blueprint rather than written again, and that is worth
+ * pausing on: `ExternalComponent` inherits fifteen required members before it reaches the two a template
+ * author cares about, so a package that redeclared those defaults would be maintaining a second copy of a
+ * decision it does not own. Borrowing the builder is the same choice as depending on the shell - this
+ * blueprint layers on the default one, so it uses its parts.
+ */ /**
+ * This blueprint's page header, given its heading and the one binding the page is about.
+ *
+ * Every template opens with one. The header derives the trail and the design-time binding state itself, so
+ * a template states the page's subject once instead of repeating it in a title, a trail and a table.
+ */ function arcPageHeader(id, options, actions = []) {
+    return scene_blueprint_default.externalComponent(id, ComponentName.ComponentName.ArcPageHeader, {
+        ...options
+    }, {
+        actions
+    });
+}
+/**
+ * The library's `page` primitive wrapping content.
+ *
+ * A `div` would have done structurally, and would have been wrong: `page` is the full-height flex column
+ * every other component in `@cratis/components` is laid out inside, drawn from the same `--cratis-*`
+ * tokens as the tables and dialogs it contains. Content wrapped in it gets that consistency for free, and
+ * content wrapped in a `div` has to reinvent it and will drift.
+ */ function page(id, title, content, panel = true) {
+    return scene_blueprint_default.externalComponent(id, CompositeName.CompositeName.Page, {
+        title,
+        showTitle: title.length > 0,
+        panel
+    }, {
+        content
+    });
+}
+/** One button in a tool palette. `title` is the accessible name as well as the tooltip, so it is never omitted. */ function toolbarButton(id, title, icon, text) {
+    return scene_blueprint_default.externalComponent(id, CompositeName.CompositeName.ToolbarButton, {
+        title,
+        icon,
+        text
+    });
+}
+/** Related buttons kept together inside a toolbar. */ function toolbarGroup(id, buttons) {
+    return scene_blueprint_default.externalComponent(id, CompositeName.CompositeName.ToolbarGroup, {
+        orientation: 'horizontal'
+    }, {
+        content: buttons
+    });
+}
+/** The divider between groups of tools. */ function toolbarSeparator(id) {
+    return scene_blueprint_default.externalComponent(id, CompositeName.CompositeName.ToolbarSeparator, {
+        orientation: 'horizontal'
+    });
+}
+/**
+ * A horizontal tool palette.
+ *
+ * `draggable` is deliberately left off rather than set per button - it is a property of the palette, and
+ * setting it per button is how you end up with a palette that is half draggable.
+ */ function toolbar(id, content) {
+    return scene_blueprint_default.externalComponent(id, CompositeName.CompositeName.Toolbar, {
+        orientation: 'horizontal'
+    }, {
+        content
+    });
+}
+/**
+ * Scopes a failure to one region of a page.
+ *
+ * React's default is that a throw anywhere unmounts the whole tree, which on a composed screen means one
+ * broken widget takes the navigation with it. Which regions deserve a boundary is a decision about the
+ * page, which is exactly why it belongs in a template rather than in the renderer.
+ */ function errorBoundary(id, content) {
+    return scene_blueprint_default.externalComponent(id, CompositeName.CompositeName.ErrorBoundary, {}, {
+        content
+    });
+}
+/** An icon, given a PrimeIcons class name. */ function icon(id, iconName) {
+    return scene_blueprint_default.externalComponent(id, CompositeName.CompositeName.Icon, {
+        icon: iconName
+    });
+}
+
+exports.arcPageHeader = arcPageHeader;
+exports.errorBoundary = errorBoundary;
+exports.icon = icon;
+exports.page = page;
+exports.toolbar = toolbar;
+exports.toolbarButton = toolbarButton;
+exports.toolbarGroup = toolbarGroup;
+exports.toolbarSeparator = toolbarSeparator;
+//# sourceMappingURL=elements.js.map

package/dist/cjs/templates/elements.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"elements.js","sources":["../../../templates/elements.ts"],"sourcesContent":["// Copyright (c) Cratis. All rights reserved.\n// Licensed under the MIT license. See LICENSE file in the project root for full license information.\n\nimport { SceneElement } from '@cratis/scene.model';\nimport { externalComponent } from '@cratis/scene.blueprint.default';\nimport { ComponentName } from '../ComponentName';\nimport { CompositeName } from '../CompositeName';\nimport { ArcHeaderOptions } from './ArcHeaderOptions';\n\n/**\n * The page furniture every template in this package repeats.\n *\n * `externalComponent` is imported from the default blueprint rather than written again, and that is worth\n * pausing on: `ExternalComponent` inherits fifteen required members before it reaches the two a template\n * author cares about, so a package that redeclared those defaults would be maintaining a second copy of a\n * decision it does not own. Borrowing the builder is the same choice as depending on the shell - this\n * blueprint layers on the default one, so it uses its parts.\n */\n\n/**\n * This blueprint's page header, given its heading and the one binding the page is about.\n *\n * Every template opens with one. The header derives the trail and the design-time binding state itself, so\n * a template states the page's subject once instead of repeating it in a title, a trail and a table.\n */\nexport function arcPageHeader(id: string, options: ArcHeaderOptions, actions: SceneElement[] = []): SceneElement {\n    return externalComponent(id, ComponentName.ArcPageHeader, { ...options }, { actions });\n}\n\n/**\n * The library's `page` primitive wrapping content.\n *\n * A `div` would have done structurally, and would have been wrong: `page` is the full-height flex column\n * every other component in `@cratis/components` is laid out inside, drawn from the same `--cratis-*`\n * tokens as the tables and dialogs it contains. Content wrapped in it gets that consistency for free, and\n * content wrapped in a `div` has to reinvent it and will drift.\n */\nexport function page(id: string, title: string, content: SceneElement[], panel = true): SceneElement {\n    return externalComponent(id, CompositeName.Page, { title, showTitle: title.length > 0, panel }, { content });\n}\n\n/** One button in a tool palette. `title` is the accessible name as well as the tooltip, so it is never omitted. */\nexport function toolbarButton(id: string, title: string, icon: string, text?: string): SceneElement {\n    return externalComponent(id, CompositeName.ToolbarButton, { title, icon, text });\n}\n\n/** Related buttons kept together inside a toolbar. */\nexport function toolbarGroup(id: string, buttons: SceneElement[]): SceneElement {\n    return externalComponent(id, CompositeName.ToolbarGroup, { orientation: 'horizontal' }, { content: buttons });\n}\n\n/** The divider between groups of tools. */\nexport function toolbarSeparator(id: string): SceneElement {\n    return externalComponent(id, CompositeName.ToolbarSeparator, { orientation: 'horizontal' });\n}\n\n/**\n * A horizontal tool palette.\n *\n * `draggable` is deliberately left off rather than set per button - it is a property of the palette, and\n * setting it per button is how you end up with a palette that is half draggable.\n */\nexport function toolbar(id: string, content: SceneElement[]): SceneElement {\n    return externalComponent(id, CompositeName.Toolbar, { orientation: 'horizontal' }, { content });\n}\n\n/**\n * Scopes a failure to one region of a page.\n *\n * React's default is that a throw anywhere unmounts the whole tree, which on a composed screen means one\n * broken widget takes the navigation with it. Which regions deserve a boundary is a decision about the\n * page, which is exactly why it belongs in a template rather than in the renderer.\n */\nexport function errorBoundary(id: string, content: SceneElement[]): SceneElement {\n    return externalComponent(id, CompositeName.ErrorBoundary, {}, { content });\n}\n\n/** An icon, given a PrimeIcons class name. */\nexport function icon(id: string, iconName: string): SceneElement {\n    return externalComponent(id, CompositeName.Icon, { icon: iconName });\n}\n"],"names":["arcPageHeader","id","options","actions","externalComponent","ComponentName","ArcPageHeader","page","title","content","panel","CompositeName","Page","showTitle","length","toolbarButton","icon","text","ToolbarButton","toolbarGroup","buttons","ToolbarGroup","orientation","toolbarSeparator","ToolbarSeparator","toolbar","Toolbar","errorBoundary","ErrorBoundary","iconName","Icon"],"mappings":";;;;;;AAAA;AACA;AAQA;;;;;;;;;;;;;IAgBO,SAASA,aAAAA,CAAcC,EAAU,EAAEC,OAAyB,EAAEC,UAA0B,EAAE,EAAA;AAC7F,IAAA,OAAOC,yCAAAA,CAAkBH,EAAAA,EAAII,2BAAAA,CAAcC,aAAa,EAAE;AAAE,QAAA,GAAGJ;KAAQ,EAAG;AAAEC,QAAAA;AAAQ,KAAA,CAAA;AACxF;AAEA;;;;;;;IAQO,SAASI,IAAAA,CAAKN,EAAU,EAAEO,KAAa,EAAEC,OAAuB,EAAEC,KAAAA,GAAQ,IAAI,EAAA;AACjF,IAAA,OAAON,yCAAAA,CAAkBH,EAAAA,EAAIU,2BAAAA,CAAcC,IAAI,EAAE;AAAEJ,QAAAA,KAAAA;QAAOK,SAAAA,EAAWL,KAAAA,CAAMM,MAAM,GAAG,CAAA;AAAGJ,QAAAA;KAAM,EAAG;AAAED,QAAAA;AAAQ,KAAA,CAAA;AAC9G;AAEA,oHACO,SAASM,aAAAA,CAAcd,EAAU,EAAEO,KAAa,EAAEQ,IAAY,EAAEC,IAAa,EAAA;AAChF,IAAA,OAAOb,yCAAAA,CAAkBH,EAAAA,EAAIU,2BAAAA,CAAcO,aAAa,EAAE;AAAEV,QAAAA,KAAAA;AAAOQ,QAAAA,IAAAA;AAAMC,QAAAA;AAAK,KAAA,CAAA;AAClF;AAEA,uDACO,SAASE,YAAAA,CAAalB,EAAU,EAAEmB,OAAuB,EAAA;AAC5D,IAAA,OAAOhB,yCAAAA,CAAkBH,EAAAA,EAAIU,2BAAAA,CAAcU,YAAY,EAAE;QAAEC,WAAAA,EAAa;KAAa,EAAG;QAAEb,OAAAA,EAASW;AAAQ,KAAA,CAAA;AAC/G;AAEA,4CACO,SAASG,gBAAAA,CAAiBtB,EAAU,EAAA;AACvC,IAAA,OAAOG,yCAAAA,CAAkBH,EAAAA,EAAIU,2BAAAA,CAAca,gBAAgB,EAAE;QAAEF,WAAAA,EAAa;AAAa,KAAA,CAAA;AAC7F;AAEA;;;;;AAKC,IACM,SAASG,OAAAA,CAAQxB,EAAU,EAAEQ,OAAuB,EAAA;AACvD,IAAA,OAAOL,yCAAAA,CAAkBH,EAAAA,EAAIU,2BAAAA,CAAce,OAAO,EAAE;QAAEJ,WAAAA,EAAa;KAAa,EAAG;AAAEb,QAAAA;AAAQ,KAAA,CAAA;AACjG;AAEA;;;;;;AAMC,IACM,SAASkB,aAAAA,CAAc1B,EAAU,EAAEQ,OAAuB,EAAA;AAC7D,IAAA,OAAOL,0CAAkBH,EAAAA,EAAIU,2BAAAA,CAAciB,aAAa,EAAE,EAAC,EAAG;AAAEnB,QAAAA;AAAQ,KAAA,CAAA;AAC5E;AAEA,+CACO,SAASO,IAAAA,CAAKf,EAAU,EAAE4B,QAAgB,EAAA;AAC7C,IAAA,OAAOzB,yCAAAA,CAAkBH,EAAAA,EAAIU,2BAAAA,CAAcmB,IAAI,EAAE;QAAEd,IAAAA,EAAMa;AAAS,KAAA,CAAA;AACtE;;;;;;;;;;;"}

package/dist/cjs/templates/formElements.js

@@ -0,0 +1,77 @@
+'use strict';
+
+var scene_blueprint_default = require('@cratis/scene.blueprint.default');
+var CompositeName = require('../CompositeName.js');
+
+// Copyright (c) Cratis. All rights reserved.
+// Licensed under the MIT license. See LICENSE file in the project root for full license information.
+/**
+ * The Arc-bound form elements this blueprint's templates are built from.
+ *
+ * Every field carries a `property` name, which the library turns into an accessor onto the command
+ * instance. That indirection is not incidental: a hand-written form binds a field with
+ * `value={command => command.number}` and is typechecked against the generated proxy, and a template has
+ * no types to check against because it is data. The name is what survives, so the name is what a field
+ * carries.
+ */ /**
+ * A whole form generated from the command's own property descriptors.
+ *
+ * `commandForm` is `AutoCommandForm`, not `CommandForm`, and that is what makes it worth shipping in a
+ * template at all: a template that listed every field by hand would go stale the moment a property was
+ * added to the command on the backend, and a stale template is worse than no template. This one follows
+ * the command, which is the same guarantee Arc's generated proxies give the rest of the stack.
+ *
+ * @param exclude Properties the surrounding template places itself, so the generated form does not produce a second copy.
+ */ function commandForm(id, command, exclude) {
+    return scene_blueprint_default.externalComponent(id, CompositeName.CompositeName.CommandForm, {
+        command,
+        exclude
+    });
+}
+/** A single-line text field bound to one command property. */ function inputTextField(id, property, title, placeholder) {
+    return scene_blueprint_default.externalComponent(id, CompositeName.CompositeName.InputTextField, {
+        property,
+        title,
+        placeholder
+    });
+}
+/** A numeric field bound to one command property. */ function numberField(id, property, title) {
+    return scene_blueprint_default.externalComponent(id, CompositeName.CompositeName.NumberField, {
+        property,
+        title
+    });
+}
+/** A multi-line text field bound to one command property. */ function textAreaField(id, property, title, rows = 3) {
+    return scene_blueprint_default.externalComponent(id, CompositeName.CompositeName.TextAreaField, {
+        property,
+        title,
+        rows
+    });
+}
+/** A date field bound to one command property. */ function calendarField(id, property, title) {
+    return scene_blueprint_default.externalComponent(id, CompositeName.CompositeName.CalendarField, {
+        property,
+        title
+    });
+}
+/**
+ * A single-selection field over a list the template carries inline.
+ *
+ * Inline options only. A list that has to come from the backend is a different thing entirely - bind it to
+ * a query - because a property bag is the wrong place for data, and a template that embedded a real
+ * lookup table would be shipping someone else's reference data.
+ */ function dropdownField(id, property, title, options) {
+    return scene_blueprint_default.externalComponent(id, CompositeName.CompositeName.DropdownField, {
+        property,
+        title,
+        options
+    });
+}
+
+exports.calendarField = calendarField;
+exports.commandForm = commandForm;
+exports.dropdownField = dropdownField;
+exports.inputTextField = inputTextField;
+exports.numberField = numberField;
+exports.textAreaField = textAreaField;
+//# sourceMappingURL=formElements.js.map

package/dist/cjs/templates/formElements.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"formElements.js","sources":["../../../templates/formElements.ts"],"sourcesContent":["// Copyright (c) Cratis. All rights reserved.\n// Licensed under the MIT license. See LICENSE file in the project root for full license information.\n\nimport { SceneElement } from '@cratis/scene.model';\nimport { externalComponent } from '@cratis/scene.blueprint.default';\nimport { CompositeName } from '../CompositeName';\n\n/**\n * The Arc-bound form elements this blueprint's templates are built from.\n *\n * Every field carries a `property` name, which the library turns into an accessor onto the command\n * instance. That indirection is not incidental: a hand-written form binds a field with\n * `value={command => command.number}` and is typechecked against the generated proxy, and a template has\n * no types to check against because it is data. The name is what survives, so the name is what a field\n * carries.\n */\n\n/**\n * A whole form generated from the command's own property descriptors.\n *\n * `commandForm` is `AutoCommandForm`, not `CommandForm`, and that is what makes it worth shipping in a\n * template at all: a template that listed every field by hand would go stale the moment a property was\n * added to the command on the backend, and a stale template is worse than no template. This one follows\n * the command, which is the same guarantee Arc's generated proxies give the rest of the stack.\n *\n * @param exclude Properties the surrounding template places itself, so the generated form does not produce a second copy.\n */\nexport function commandForm(id: string, command: string, exclude?: string[]): SceneElement {\n    return externalComponent(id, CompositeName.CommandForm, { command, exclude });\n}\n\n/** A single-line text field bound to one command property. */\nexport function inputTextField(id: string, property: string, title: string, placeholder?: string): SceneElement {\n    return externalComponent(id, CompositeName.InputTextField, { property, title, placeholder });\n}\n\n/** A numeric field bound to one command property. */\nexport function numberField(id: string, property: string, title: string): SceneElement {\n    return externalComponent(id, CompositeName.NumberField, { property, title });\n}\n\n/** A multi-line text field bound to one command property. */\nexport function textAreaField(id: string, property: string, title: string, rows = 3): SceneElement {\n    return externalComponent(id, CompositeName.TextAreaField, { property, title, rows });\n}\n\n/** A date field bound to one command property. */\nexport function calendarField(id: string, property: string, title: string): SceneElement {\n    return externalComponent(id, CompositeName.CalendarField, { property, title });\n}\n\n/**\n * A single-selection field over a list the template carries inline.\n *\n * Inline options only. A list that has to come from the backend is a different thing entirely - bind it to\n * a query - because a property bag is the wrong place for data, and a template that embedded a real\n * lookup table would be shipping someone else's reference data.\n */\nexport function dropdownField(id: string, property: string, title: string, options: { label: string; value: string }[]): SceneElement {\n    return externalComponent(id, CompositeName.DropdownField, { property, title, options });\n}\n"],"names":["commandForm","id","command","exclude","externalComponent","CompositeName","CommandForm","inputTextField","property","title","placeholder","InputTextField","numberField","NumberField","textAreaField","rows","TextAreaField","calendarField","CalendarField","dropdownField","options","DropdownField"],"mappings":";;;;;AAAA;AACA;AAMA;;;;;;;;;;;;;;;;;AAmBC,IACM,SAASA,WAAAA,CAAYC,EAAU,EAAEC,OAAe,EAAEC,OAAkB,EAAA;AACvE,IAAA,OAAOC,yCAAAA,CAAkBH,EAAAA,EAAII,2BAAAA,CAAcC,WAAW,EAAE;AAAEJ,QAAAA,OAAAA;AAASC,QAAAA;AAAQ,KAAA,CAAA;AAC/E;AAEA,+DACO,SAASI,cAAAA,CAAeN,EAAU,EAAEO,QAAgB,EAAEC,KAAa,EAAEC,WAAoB,EAAA;AAC5F,IAAA,OAAON,yCAAAA,CAAkBH,EAAAA,EAAII,2BAAAA,CAAcM,cAAc,EAAE;AAAEH,QAAAA,QAAAA;AAAUC,QAAAA,KAAAA;AAAOC,QAAAA;AAAY,KAAA,CAAA;AAC9F;AAEA,sDACO,SAASE,WAAAA,CAAYX,EAAU,EAAEO,QAAgB,EAAEC,KAAa,EAAA;AACnE,IAAA,OAAOL,yCAAAA,CAAkBH,EAAAA,EAAII,2BAAAA,CAAcQ,WAAW,EAAE;AAAEL,QAAAA,QAAAA;AAAUC,QAAAA;AAAM,KAAA,CAAA;AAC9E;AAEA,8DACO,SAASK,aAAAA,CAAcb,EAAU,EAAEO,QAAgB,EAAEC,KAAa,EAAEM,IAAAA,GAAO,CAAC,EAAA;AAC/E,IAAA,OAAOX,yCAAAA,CAAkBH,EAAAA,EAAII,2BAAAA,CAAcW,aAAa,EAAE;AAAER,QAAAA,QAAAA;AAAUC,QAAAA,KAAAA;AAAOM,QAAAA;AAAK,KAAA,CAAA;AACtF;AAEA,mDACO,SAASE,aAAAA,CAAchB,EAAU,EAAEO,QAAgB,EAAEC,KAAa,EAAA;AACrE,IAAA,OAAOL,yCAAAA,CAAkBH,EAAAA,EAAII,2BAAAA,CAAca,aAAa,EAAE;AAAEV,QAAAA,QAAAA;AAAUC,QAAAA;AAAM,KAAA,CAAA;AAChF;AAEA;;;;;;IAOO,SAASU,aAAAA,CAAclB,EAAU,EAAEO,QAAgB,EAAEC,KAAa,EAAEW,OAA2C,EAAA;AAClH,IAAA,OAAOhB,yCAAAA,CAAkBH,EAAAA,EAAII,2BAAAA,CAAcgB,aAAa,EAAE;AAAEb,QAAAA,QAAAA;AAAUC,QAAAA,KAAAA;AAAOW,QAAAA;AAAQ,KAAA,CAAA;AACzF;;;;;;;;;"}

package/dist/cjs/templates/listTemplates.js

@@ -0,0 +1,187 @@
+'use strict';
+
+var scene_model = require('@cratis/scene.model');
+var scene_blueprint_default = require('@cratis/scene.blueprint.default');
+var dataElements = require('./dataElements.js');
+var editorElements = require('./editorElements.js');
+var elements = require('./elements.js');
+var SampleBindingName = require('./SampleBindingName.js');
+
+// Copyright (c) Cratis. All rights reserved.
+// Licensed under the MIT license. See LICENSE file in the project root for full license information.
+/**
+ * The three list shapes an Arc application repeats: a list, a live list, and a list with the selected
+ * record beside it.
+ *
+ * All three fill the application shell's `content` slot, which is the only slot the default blueprint's
+ * `AppShell` layout declares for a screen - so an application that has picked the default blueprint can
+ * drop any of these in without arranging anything.
+ *
+ * What makes them worth shipping is what is *already wired*. A list page is not "a table in a slot"; it is
+ * a query name, a set of columns, an empty message, a data key, a filter field list, a header that states
+ * what the page is bound to, and an action bar. Every one of those is a decision, and repeating all seven
+ * per screen is how a list page ends up subtly different on every screen of an application.
+ */ /**
+ * The archetype: a `dataPage` filling the body, under a header that says what it is bound to.
+ *
+ * `dataPage` is the single highest-leverage name `Cratis.Components` exposes - the library's whole
+ * list-screen composite, with its title bar, menubar, filterable table and optional details pane driven
+ * from one query. Building the same thing out of a `table` and a `toolbar` in a screen is pages of
+ * modeling for a worse result, and this template is the answer to that: an application supplies a query
+ * name and has a working list page.
+ */ const dataListPageTemplate = {
+    name: 'DataListPage',
+    fitsSlot: scene_blueprint_default.SlotName.Content,
+    slots: [
+        {
+            name: scene_blueprint_default.TemplateSlotName.Header
+        },
+        {
+            name: scene_blueprint_default.TemplateSlotName.Body
+        }
+    ],
+    content: {
+        [scene_blueprint_default.TemplateSlotName.Header]: [
+            elements.arcPageHeader('data-list-header', {
+                title: 'Invoices',
+                subtitle: 'Every invoice, filterable and paged against the server',
+                section: 'Billing',
+                query: SampleBindingName.SampleBindingName.AllInvoices
+            }, [
+                elements.toolbar('data-list-actions', [
+                    elements.toolbarButton('data-list-new', 'Register an invoice', 'pi pi-plus', 'New'),
+                    elements.toolbarButton('data-list-refresh', 'Refresh', 'pi pi-refresh'),
+                    elements.toolbarSeparator('data-list-separator'),
+                    elements.toolbarGroup('data-list-export', [
+                        elements.toolbarButton('data-list-download', 'Download as CSV', 'pi pi-download'),
+                        elements.toolbarButton('data-list-print', 'Print', 'pi pi-print')
+                    ])
+                ])
+            ])
+        ],
+        [scene_blueprint_default.TemplateSlotName.Body]: [
+            dataElements.dataPage('data-list-body', SampleBindingName.SampleBindingName.AllInvoices, dataElements.invoiceTableOptions, dataElements.invoiceColumns)
+        ]
+    },
+    displayName: 'Data list page',
+    description: 'A dataPage bound to one query, under a header that states the binding - the whole list screen in two elements.'
+};
+/**
+ * The live variant: the same page shape over an observable query.
+ *
+ * A separate template rather than a flag, for the same reason `observableDataTable` is a separate name
+ * from `dataTable`: the difference lives in the *proxy* a host registers, not in how the page is
+ * configured. An observable query opens a subscription and the page re-renders when the read model
+ * changes on the server. Choosing this template is an application saying its data is live, and that is a
+ * decision worth being able to read off the screen rather than infer from a property.
+ */ const observableDataListPageTemplate = {
+    name: 'ObservableDataListPage',
+    fitsSlot: scene_blueprint_default.SlotName.Content,
+    slots: [
+        {
+            name: scene_blueprint_default.TemplateSlotName.Header
+        },
+        {
+            name: scene_blueprint_default.TemplateSlotName.Body
+        }
+    ],
+    content: {
+        [scene_blueprint_default.TemplateSlotName.Header]: [
+            elements.arcPageHeader('observable-list-header', {
+                title: 'Invoices in flight',
+                subtitle: 'Updates as the read model changes - no refresh button, because there is nothing to refresh',
+                section: 'Billing',
+                query: SampleBindingName.SampleBindingName.InvoicesInFlight
+            })
+        ],
+        [scene_blueprint_default.TemplateSlotName.Body]: [
+            elements.page('observable-list-body', 'In flight', [
+                dataElements.observableDataTable('observable-list-table', SampleBindingName.SampleBindingName.InvoicesInFlight, dataElements.invoiceTableOptions, dataElements.invoiceColumns)
+            ])
+        ]
+    },
+    displayName: 'Observable data list page',
+    description: 'A live list over an observable query, which re-renders when the read model changes on the server.'
+};
+/**
+ * List plus detail: the whole list screen, with the selected record's document and history beside it.
+ *
+ * The detail region is built from the library's Arc-free editors, which is the interesting part. They read
+ * their content out of the property bag rather than from a query, so this half of the page renders fully
+ * at design time while the list half is still a placeholder - and in an event-sourced application the
+ * record's *history* is as natural a thing to show as its current values, which is why the time machine is
+ * here rather than in some optional extra.
+ *
+ * Its arrangement drops the detail column below the list at a compact width, because a document editor and
+ * a paged table side by side on a phone are two unreadable slivers.
+ */ const dataListWithDetailPageTemplate = {
+    name: 'DataListWithDetailPage',
+    fitsSlot: scene_blueprint_default.SlotName.Content,
+    slots: [
+        {
+            name: scene_blueprint_default.TemplateSlotName.Header
+        },
+        {
+            name: scene_blueprint_default.TemplateSlotName.Body
+        },
+        {
+            name: scene_blueprint_default.TemplateSlotName.SidePanel
+        }
+    ],
+    arrangement: {
+        root: scene_blueprint_default.column([
+            scene_blueprint_default.slotLeaf(scene_blueprint_default.TemplateSlotName.Header),
+            scene_blueprint_default.row([
+                scene_blueprint_default.slotLeaf(scene_blueprint_default.TemplateSlotName.Body, {
+                    grow: 2
+                }),
+                scene_blueprint_default.slotLeaf(scene_blueprint_default.TemplateSlotName.SidePanel, {
+                    grow: 1
+                })
+            ], 16)
+        ]),
+        overrides: [
+            {
+                width: scene_model.WidthSizeClass.Compact,
+                root: scene_blueprint_default.column([
+                    scene_blueprint_default.slotLeaf(scene_blueprint_default.TemplateSlotName.Header),
+                    scene_blueprint_default.slotLeaf(scene_blueprint_default.TemplateSlotName.Body),
+                    scene_blueprint_default.slotLeaf(scene_blueprint_default.TemplateSlotName.SidePanel)
+                ], 16)
+            }
+        ]
+    },
+    content: {
+        [scene_blueprint_default.TemplateSlotName.Header]: [
+            elements.arcPageHeader('list-detail-header', {
+                title: 'Invoices',
+                subtitle: 'The list, with the selected invoice beside it',
+                section: 'Billing',
+                query: SampleBindingName.SampleBindingName.AllInvoices
+            })
+        ],
+        [scene_blueprint_default.TemplateSlotName.Body]: [
+            dataElements.dataPage('list-detail-body', SampleBindingName.SampleBindingName.AllInvoices, dataElements.invoiceTableOptions, dataElements.invoiceColumns)
+        ],
+        [scene_blueprint_default.TemplateSlotName.SidePanel]: [
+            elements.page('list-detail-panel', 'Selected invoice', [
+                editorElements.objectNavigationalBar('list-detail-trail'),
+                editorElements.objectContentEditor('list-detail-document', false),
+                editorElements.timeMachine('list-detail-history')
+            ])
+        ]
+    },
+    displayName: 'Data list with detail page',
+    description: 'A dataPage beside a detail region showing the selected record document and its history.'
+};
+/** The three list-shaped templates. */ const listTemplates = [
+    dataListPageTemplate,
+    observableDataListPageTemplate,
+    dataListWithDetailPageTemplate
+];
+
+exports.dataListPageTemplate = dataListPageTemplate;
+exports.dataListWithDetailPageTemplate = dataListWithDetailPageTemplate;
+exports.listTemplates = listTemplates;
+exports.observableDataListPageTemplate = observableDataListPageTemplate;
+//# sourceMappingURL=listTemplates.js.map

package/dist/cjs/templates/listTemplates.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"listTemplates.js","sources":["../../../templates/listTemplates.ts"],"sourcesContent":["// Copyright (c) Cratis. All rights reserved.\n// Licensed under the MIT license. See LICENSE file in the project root for full license information.\n\nimport { ScreenTemplate, WidthSizeClass } from '@cratis/scene.model';\nimport { SlotName, TemplateSlotName, column, row, slotLeaf } from '@cratis/scene.blueprint.default';\nimport { dataPage, invoiceColumns, invoiceTableOptions, observableDataTable } from './dataElements';\nimport { objectContentEditor, objectNavigationalBar, timeMachine } from './editorElements';\nimport { arcPageHeader, page, toolbar, toolbarButton, toolbarGroup, toolbarSeparator } from './elements';\nimport { SampleBindingName } from './SampleBindingName';\n\n/**\n * The three list shapes an Arc application repeats: a list, a live list, and a list with the selected\n * record beside it.\n *\n * All three fill the application shell's `content` slot, which is the only slot the default blueprint's\n * `AppShell` layout declares for a screen - so an application that has picked the default blueprint can\n * drop any of these in without arranging anything.\n *\n * What makes them worth shipping is what is *already wired*. A list page is not \"a table in a slot\"; it is\n * a query name, a set of columns, an empty message, a data key, a filter field list, a header that states\n * what the page is bound to, and an action bar. Every one of those is a decision, and repeating all seven\n * per screen is how a list page ends up subtly different on every screen of an application.\n */\n\n/**\n * The archetype: a `dataPage` filling the body, under a header that says what it is bound to.\n *\n * `dataPage` is the single highest-leverage name `Cratis.Components` exposes - the library's whole\n * list-screen composite, with its title bar, menubar, filterable table and optional details pane driven\n * from one query. Building the same thing out of a `table` and a `toolbar` in a screen is pages of\n * modeling for a worse result, and this template is the answer to that: an application supplies a query\n * name and has a working list page.\n */\nexport const dataListPageTemplate: ScreenTemplate = {\n    name: 'DataListPage',\n    fitsSlot: SlotName.Content,\n    slots: [{ name: TemplateSlotName.Header }, { name: TemplateSlotName.Body }],\n    content: {\n        [TemplateSlotName.Header]: [\n            arcPageHeader(\n                'data-list-header',\n                { title: 'Invoices', subtitle: 'Every invoice, filterable and paged against the server', section: 'Billing', query: SampleBindingName.AllInvoices },\n                [\n                    toolbar('data-list-actions', [\n                        toolbarButton('data-list-new', 'Register an invoice', 'pi pi-plus', 'New'),\n                        toolbarButton('data-list-refresh', 'Refresh', 'pi pi-refresh'),\n                        toolbarSeparator('data-list-separator'),\n                        toolbarGroup('data-list-export', [\n                            toolbarButton('data-list-download', 'Download as CSV', 'pi pi-download'),\n                            toolbarButton('data-list-print', 'Print', 'pi pi-print'),\n                        ]),\n                    ]),\n                ],\n            ),\n        ],\n        [TemplateSlotName.Body]: [dataPage('data-list-body', SampleBindingName.AllInvoices, invoiceTableOptions, invoiceColumns)],\n    },\n    displayName: 'Data list page',\n    description: 'A dataPage bound to one query, under a header that states the binding - the whole list screen in two elements.',\n};\n\n/**\n * The live variant: the same page shape over an observable query.\n *\n * A separate template rather than a flag, for the same reason `observableDataTable` is a separate name\n * from `dataTable`: the difference lives in the *proxy* a host registers, not in how the page is\n * configured. An observable query opens a subscription and the page re-renders when the read model\n * changes on the server. Choosing this template is an application saying its data is live, and that is a\n * decision worth being able to read off the screen rather than infer from a property.\n */\nexport const observableDataListPageTemplate: ScreenTemplate = {\n    name: 'ObservableDataListPage',\n    fitsSlot: SlotName.Content,\n    slots: [{ name: TemplateSlotName.Header }, { name: TemplateSlotName.Body }],\n    content: {\n        [TemplateSlotName.Header]: [\n            arcPageHeader('observable-list-header', {\n                title: 'Invoices in flight',\n                subtitle: 'Updates as the read model changes - no refresh button, because there is nothing to refresh',\n                section: 'Billing',\n                query: SampleBindingName.InvoicesInFlight,\n            }),\n        ],\n        [TemplateSlotName.Body]: [\n            page('observable-list-body', 'In flight', [\n                observableDataTable('observable-list-table', SampleBindingName.InvoicesInFlight, invoiceTableOptions, invoiceColumns),\n            ]),\n        ],\n    },\n    displayName: 'Observable data list page',\n    description: 'A live list over an observable query, which re-renders when the read model changes on the server.',\n};\n\n/**\n * List plus detail: the whole list screen, with the selected record's document and history beside it.\n *\n * The detail region is built from the library's Arc-free editors, which is the interesting part. They read\n * their content out of the property bag rather than from a query, so this half of the page renders fully\n * at design time while the list half is still a placeholder - and in an event-sourced application the\n * record's *history* is as natural a thing to show as its current values, which is why the time machine is\n * here rather than in some optional extra.\n *\n * Its arrangement drops the detail column below the list at a compact width, because a document editor and\n * a paged table side by side on a phone are two unreadable slivers.\n */\nexport const dataListWithDetailPageTemplate: ScreenTemplate = {\n    name: 'DataListWithDetailPage',\n    fitsSlot: SlotName.Content,\n    slots: [{ name: TemplateSlotName.Header }, { name: TemplateSlotName.Body }, { name: TemplateSlotName.SidePanel }],\n    arrangement: {\n        root: column([slotLeaf(TemplateSlotName.Header), row([slotLeaf(TemplateSlotName.Body, { grow: 2 }), slotLeaf(TemplateSlotName.SidePanel, { grow: 1 })], 16)]),\n        overrides: [\n            {\n                width: WidthSizeClass.Compact,\n                root: column([slotLeaf(TemplateSlotName.Header), slotLeaf(TemplateSlotName.Body), slotLeaf(TemplateSlotName.SidePanel)], 16),\n            },\n        ],\n    },\n    content: {\n        [TemplateSlotName.Header]: [\n            arcPageHeader('list-detail-header', {\n                title: 'Invoices',\n                subtitle: 'The list, with the selected invoice beside it',\n                section: 'Billing',\n                query: SampleBindingName.AllInvoices,\n            }),\n        ],\n        [TemplateSlotName.Body]: [dataPage('list-detail-body', SampleBindingName.AllInvoices, invoiceTableOptions, invoiceColumns)],\n        [TemplateSlotName.SidePanel]: [\n            page('list-detail-panel', 'Selected invoice', [\n                objectNavigationalBar('list-detail-trail'),\n                objectContentEditor('list-detail-document', false),\n                timeMachine('list-detail-history'),\n            ]),\n        ],\n    },\n    displayName: 'Data list with detail page',\n    description: 'A dataPage beside a detail region showing the selected record document and its history.',\n};\n\n/** The three list-shaped templates. */\nexport const listTemplates: ScreenTemplate[] = [dataListPageTemplate, observableDataListPageTemplate, dataListWithDetailPageTemplate];\n"],"names":["dataListPageTemplate","name","fitsSlot","SlotName","Content","slots","TemplateSlotName","Header","Body","content","arcPageHeader","title","subtitle","section","query","SampleBindingName","AllInvoices","toolbar","toolbarButton","toolbarSeparator","toolbarGroup","dataPage","invoiceTableOptions","invoiceColumns","displayName","description","observableDataListPageTemplate","InvoicesInFlight","page","observableDataTable","dataListWithDetailPageTemplate","SidePanel","arrangement","root","column","slotLeaf","row","grow","overrides","width","WidthSizeClass","Compact","objectNavigationalBar","objectContentEditor","timeMachine","listTemplates"],"mappings":";;;;;;;;;AAAA;AACA;AASA;;;;;;;;;;;;;;;;;;;;UAuBaA,oBAAAA,GAAuC;IAChDC,IAAAA,EAAM,cAAA;AACNC,IAAAA,QAAAA,EAAUC,iCAASC,OAAO;IAC1BC,KAAAA,EAAO;AAAC,QAAA;AAAEJ,YAAAA,IAAAA,EAAMK,yCAAiBC;AAAO,SAAA;AAAG,QAAA;AAAEN,YAAAA,IAAAA,EAAMK,yCAAiBE;AAAK;AAAE,KAAA;IAC3EC,OAAAA,EAAS;QACL,CAACH,wCAAAA,CAAiBC,MAAM,GAAG;AACvBG,YAAAA,sBAAAA,CACI,kBAAA,EACA;gBAAEC,KAAAA,EAAO,UAAA;gBAAYC,QAAAA,EAAU,wDAAA;gBAA0DC,OAAAA,EAAS,SAAA;AAAWC,gBAAAA,KAAAA,EAAOC,oCAAkBC;aAAY,EAClJ;AACIC,gBAAAA,gBAAAA,CAAQ,mBAAA,EAAqB;oBACzBC,sBAAAA,CAAc,eAAA,EAAiB,uBAAuB,YAAA,EAAc,KAAA,CAAA;AACpEA,oBAAAA,sBAAAA,CAAc,qBAAqB,SAAA,EAAW,eAAA,CAAA;oBAC9CC,yBAAAA,CAAiB,qBAAA,CAAA;AACjBC,oBAAAA,qBAAAA,CAAa,kBAAA,EAAoB;AAC7BF,wBAAAA,sBAAAA,CAAc,sBAAsB,iBAAA,EAAmB,gBAAA,CAAA;AACvDA,wBAAAA,sBAAAA,CAAc,mBAAmB,OAAA,EAAS,aAAA;AAC7C,qBAAA;AACJ,iBAAA;AACJ,aAAA;AAER,SAAA;QACD,CAACZ,wCAAAA,CAAiBE,IAAI,GAAG;AAACa,YAAAA,qBAAAA,CAAS,gBAAA,EAAkBN,mCAAAA,CAAkBC,WAAW,EAAEM,gCAAAA,EAAqBC,2BAAAA;AAAgB;AAC7H,KAAA;IACAC,WAAAA,EAAa,gBAAA;IACbC,WAAAA,EAAa;AACjB;AAEA;;;;;;;;UASaC,8BAAAA,GAAiD;IAC1DzB,IAAAA,EAAM,wBAAA;AACNC,IAAAA,QAAAA,EAAUC,iCAASC,OAAO;IAC1BC,KAAAA,EAAO;AAAC,QAAA;AAAEJ,YAAAA,IAAAA,EAAMK,yCAAiBC;AAAO,SAAA;AAAG,QAAA;AAAEN,YAAAA,IAAAA,EAAMK,yCAAiBE;AAAK;AAAE,KAAA;IAC3EC,OAAAA,EAAS;QACL,CAACH,wCAAAA,CAAiBC,MAAM,GAAG;AACvBG,YAAAA,sBAAAA,CAAc,wBAAA,EAA0B;gBACpCC,KAAAA,EAAO,oBAAA;gBACPC,QAAAA,EAAU,4FAAA;gBACVC,OAAAA,EAAS,SAAA;AACTC,gBAAAA,KAAAA,EAAOC,oCAAkBY;AAC7B,aAAA;AACH,SAAA;QACD,CAACrB,wCAAAA,CAAiBE,IAAI,GAAG;AACrBoB,YAAAA,aAAAA,CAAK,wBAAwB,WAAA,EAAa;AACtCC,gBAAAA,gCAAAA,CAAoB,uBAAA,EAAyBd,mCAAAA,CAAkBY,gBAAgB,EAAEL,gCAAAA,EAAqBC,2BAAAA;AACzG,aAAA;AACJ;AACL,KAAA;IACAC,WAAAA,EAAa,2BAAA;IACbC,WAAAA,EAAa;AACjB;AAEA;;;;;;;;;;;UAYaK,8BAAAA,GAAiD;IAC1D7B,IAAAA,EAAM,wBAAA;AACNC,IAAAA,QAAAA,EAAUC,iCAASC,OAAO;IAC1BC,KAAAA,EAAO;AAAC,QAAA;AAAEJ,YAAAA,IAAAA,EAAMK,yCAAiBC;AAAO,SAAA;AAAG,QAAA;AAAEN,YAAAA,IAAAA,EAAMK,yCAAiBE;AAAK,SAAA;AAAG,QAAA;AAAEP,YAAAA,IAAAA,EAAMK,yCAAiByB;AAAU;AAAE,KAAA;IACjHC,WAAAA,EAAa;AACTC,QAAAA,IAAAA,EAAMC,8BAAAA,CAAO;AAACC,YAAAA,gCAAAA,CAAS7B,yCAAiBC,MAAM,CAAA;YAAG6B,2BAAAA,CAAI;gBAACD,gCAAAA,CAAS7B,wCAAAA,CAAiBE,IAAI,EAAE;oBAAE6B,IAAAA,EAAM;AAAE,iBAAA,CAAA;gBAAIF,gCAAAA,CAAS7B,wCAAAA,CAAiByB,SAAS,EAAE;oBAAEM,IAAAA,EAAM;AAAE,iBAAA;aAAG,EAAE,EAAA;AAAI,SAAA,CAAA;QAC5JC,SAAAA,EAAW;AACP,YAAA;AACIC,gBAAAA,KAAAA,EAAOC,2BAAeC,OAAO;AAC7BR,gBAAAA,IAAAA,EAAMC,8BAAAA,CAAO;AAACC,oBAAAA,gCAAAA,CAAS7B,yCAAiBC,MAAM,CAAA;AAAG4B,oBAAAA,gCAAAA,CAAS7B,yCAAiBE,IAAI,CAAA;AAAG2B,oBAAAA,gCAAAA,CAAS7B,yCAAiByB,SAAS;iBAAE,EAAE,EAAA;AAC7H;AACH;AACL,KAAA;IACAtB,OAAAA,EAAS;QACL,CAACH,wCAAAA,CAAiBC,MAAM,GAAG;AACvBG,YAAAA,sBAAAA,CAAc,oBAAA,EAAsB;gBAChCC,KAAAA,EAAO,UAAA;gBACPC,QAAAA,EAAU,+CAAA;gBACVC,OAAAA,EAAS,SAAA;AACTC,gBAAAA,KAAAA,EAAOC,oCAAkBC;AAC7B,aAAA;AACH,SAAA;QACD,CAACV,wCAAAA,CAAiBE,IAAI,GAAG;AAACa,YAAAA,qBAAAA,CAAS,kBAAA,EAAoBN,mCAAAA,CAAkBC,WAAW,EAAEM,gCAAAA,EAAqBC,2BAAAA;AAAgB,SAAA;QAC3H,CAACjB,wCAAAA,CAAiByB,SAAS,GAAG;AAC1BH,YAAAA,aAAAA,CAAK,qBAAqB,kBAAA,EAAoB;gBAC1Cc,oCAAAA,CAAsB,mBAAA,CAAA;AACtBC,gBAAAA,kCAAAA,CAAoB,sBAAA,EAAwB,KAAA,CAAA;gBAC5CC,0BAAAA,CAAY,qBAAA;AACf,aAAA;AACJ;AACL,KAAA;IACApB,WAAAA,EAAa,4BAAA;IACbC,WAAAA,EAAa;AACjB;AAEA,wCACO,MAAMoB,aAAAA,GAAkC;AAAC7C,IAAAA,oBAAAA;AAAsB0B,IAAAA,8BAAAA;AAAgCI,IAAAA;;;;;;;;"}

package/dist/cjs/templates/nesting.js

@@ -0,0 +1,150 @@
+'use strict';
+
+var scene_blueprint_default = require('@cratis/scene.blueprint.default');
+var dataElements = require('./dataElements.js');
+var editorElements = require('./editorElements.js');
+var elements = require('./elements.js');
+var SampleBindingName = require('./SampleBindingName.js');
+
+// Copyright (c) Cratis. All rights reserved.
+// Licensed under the MIT license. See LICENSE file in the project root for full license information.
+/**
+ * A worked three-level chain, from the application layout down to one behavior.
+ *
+ * The nesting rule is one rule applied at every depth: a template names, in `fitsSlot`, a slot declared by
+ * whatever contains it. A module's template fits the application layout's `content`; a feature's fits a
+ * slot the module's declares; a slice's fits one the feature's declares. Nothing here is a special case
+ * for a particular level, which is exactly why the hierarchy can be arbitrarily deep with no second
+ * mechanism.
+ *
+ * The slot names are chosen so that each fitted name is declared by exactly one container in the chain -
+ * `body` only by the module, `primary` only by the feature. That is not decoration: `resolveScreenTemplates`
+ * places a template only when the containers in scope agree on exactly one home for it, and reports it as
+ * unplaced rather than guessing when two of them declare the same name. A chain that reused `body` at
+ * three levels would read fine and resolve to nothing.
+ *
+ * The whole chain is Arc-bound, which is the point of it living in *this* blueprint rather than being a
+ * second copy of the default one's. It ends where a Cratis slice really ends: a button that summons the
+ * command dialog.
+ */ /**
+ * Module level: fits the application shell's `content` slot.
+ *
+ * A module always has a name and a description, so it brings its own header, and it offers a body for the
+ * feature inside it plus a side panel for the filters that apply across the whole module.
+ */ const dataModulePageTemplate = {
+    name: 'DataModulePage',
+    fitsSlot: scene_blueprint_default.SlotName.Content,
+    slots: [
+        {
+            name: scene_blueprint_default.TemplateSlotName.Header
+        },
+        {
+            name: scene_blueprint_default.TemplateSlotName.Body
+        },
+        {
+            name: scene_blueprint_default.TemplateSlotName.SidePanel
+        }
+    ],
+    content: {
+        [scene_blueprint_default.TemplateSlotName.Header]: [
+            elements.arcPageHeader('module-header', {
+                title: 'Billing',
+                subtitle: 'Everything the billing module owns',
+                section: 'Operations'
+            })
+        ],
+        [scene_blueprint_default.TemplateSlotName.SidePanel]: [
+            elements.page('module-filters', 'Filters', [
+                editorElements.filterPanel('module-filter-panel', 'Filter the module')
+            ])
+        ]
+    },
+    displayName: 'Data module page',
+    description: 'Module level: fits the application layout content slot and offers a body for one feature.'
+};
+/**
+ * Feature level: fits the module page's `body` slot.
+ *
+ * A feature is where actions belong - a module is a grouping and a slice is one behavior, and the feature
+ * in between is what a user thinks of as "the screen with the buttons on it". It offers a primary region
+ * for the slice and a secondary one for the live view of what that slice is doing.
+ */ const dataFeatureSectionTemplate = {
+    name: 'DataFeatureSection',
+    fitsSlot: scene_blueprint_default.TemplateSlotName.Body,
+    slots: [
+        {
+            name: scene_blueprint_default.TemplateSlotName.Toolbar
+        },
+        {
+            name: scene_blueprint_default.TemplateSlotName.Primary
+        },
+        {
+            name: scene_blueprint_default.TemplateSlotName.Secondary
+        }
+    ],
+    content: {
+        [scene_blueprint_default.TemplateSlotName.Toolbar]: [
+            elements.toolbar('feature-toolbar', [
+                elements.toolbarButton('feature-new', 'Register an invoice', 'pi pi-plus', 'New'),
+                elements.toolbarButton('feature-adjust', 'Record an adjustment', 'pi pi-pencil', 'Adjust'),
+                elements.toolbarSeparator('feature-separator'),
+                elements.toolbarButton('feature-export', 'Export the feature data', 'pi pi-download')
+            ])
+        ],
+        [scene_blueprint_default.TemplateSlotName.Secondary]: [
+            elements.page('feature-live', 'In flight', [
+                dataElements.observableDataTable('feature-live-table', SampleBindingName.SampleBindingName.InvoicesInFlight, dataElements.invoiceTableOptions, dataElements.invoiceColumns)
+            ])
+        ]
+    },
+    displayName: 'Data feature section',
+    description: 'Feature level: fits a module page body slot, brings the action toolbar and a live view.'
+};
+/**
+ * Slice level: fits the feature section's `primary` slot.
+ *
+ * The end of the chain, and deliberately the thinnest thing in it. A slice is one behavior, and in a
+ * Cratis application that behavior is one command - so its surface is a header saying what the command is
+ * and whether it is wired, and the action that summons it. The capture itself happens in the `CommandDialog`
+ * dialog template, which is why this template has no form on it and does not need one.
+ */ const commandSliceSectionTemplate = {
+    name: 'CommandSliceSection',
+    fitsSlot: scene_blueprint_default.TemplateSlotName.Primary,
+    slots: [
+        {
+            name: scene_blueprint_default.TemplateSlotName.Header
+        },
+        {
+            name: scene_blueprint_default.TemplateSlotName.Actions
+        }
+    ],
+    content: {
+        [scene_blueprint_default.TemplateSlotName.Header]: [
+            elements.arcPageHeader('slice-header', {
+                title: 'Record an adjustment',
+                subtitle: 'One behavior, one command, one button',
+                section: 'Adjustments',
+                command: SampleBindingName.SampleBindingName.RecordAdjustment
+            })
+        ],
+        [scene_blueprint_default.TemplateSlotName.Actions]: [
+            elements.toolbar('slice-actions', [
+                elements.toolbarButton('slice-record', 'Record an adjustment', 'pi pi-check', 'Record'),
+                elements.toolbarButton('slice-cancel', 'Leave the invoice as it is', 'pi pi-times', 'Cancel')
+            ])
+        ]
+    },
+    displayName: 'Command slice section',
+    description: 'Slice level: fits a feature section primary slot and hosts one command behavior.'
+};
+/** The chain, outermost first - what a spec walks to prove `fitsSlot` resolves at every level. */ const nestingChainTemplates = [
+    dataModulePageTemplate,
+    dataFeatureSectionTemplate,
+    commandSliceSectionTemplate
+];
+
+exports.commandSliceSectionTemplate = commandSliceSectionTemplate;
+exports.dataFeatureSectionTemplate = dataFeatureSectionTemplate;
+exports.dataModulePageTemplate = dataModulePageTemplate;
+exports.nestingChainTemplates = nestingChainTemplates;
+//# sourceMappingURL=nesting.js.map

package/dist/cjs/templates/nesting.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"nesting.js","sources":["../../../templates/nesting.ts"],"sourcesContent":["// Copyright (c) Cratis. All rights reserved.\n// Licensed under the MIT license. See LICENSE file in the project root for full license information.\n\nimport { ScreenTemplate } from '@cratis/scene.model';\nimport { SlotName, TemplateSlotName } from '@cratis/scene.blueprint.default';\nimport { invoiceColumns, invoiceTableOptions, observableDataTable } from './dataElements';\nimport { filterPanel } from './editorElements';\nimport { arcPageHeader, page, toolbar, toolbarButton, toolbarSeparator } from './elements';\nimport { SampleBindingName } from './SampleBindingName';\n\n/**\n * A worked three-level chain, from the application layout down to one behavior.\n *\n * The nesting rule is one rule applied at every depth: a template names, in `fitsSlot`, a slot declared by\n * whatever contains it. A module's template fits the application layout's `content`; a feature's fits a\n * slot the module's declares; a slice's fits one the feature's declares. Nothing here is a special case\n * for a particular level, which is exactly why the hierarchy can be arbitrarily deep with no second\n * mechanism.\n *\n * The slot names are chosen so that each fitted name is declared by exactly one container in the chain -\n * `body` only by the module, `primary` only by the feature. That is not decoration: `resolveScreenTemplates`\n * places a template only when the containers in scope agree on exactly one home for it, and reports it as\n * unplaced rather than guessing when two of them declare the same name. A chain that reused `body` at\n * three levels would read fine and resolve to nothing.\n *\n * The whole chain is Arc-bound, which is the point of it living in *this* blueprint rather than being a\n * second copy of the default one's. It ends where a Cratis slice really ends: a button that summons the\n * command dialog.\n */\n\n/**\n * Module level: fits the application shell's `content` slot.\n *\n * A module always has a name and a description, so it brings its own header, and it offers a body for the\n * feature inside it plus a side panel for the filters that apply across the whole module.\n */\nexport const dataModulePageTemplate: ScreenTemplate = {\n    name: 'DataModulePage',\n    fitsSlot: SlotName.Content,\n    slots: [{ name: TemplateSlotName.Header }, { name: TemplateSlotName.Body }, { name: TemplateSlotName.SidePanel }],\n    content: {\n        [TemplateSlotName.Header]: [\n            arcPageHeader('module-header', {\n                title: 'Billing',\n                subtitle: 'Everything the billing module owns',\n                section: 'Operations',\n            }),\n        ],\n        [TemplateSlotName.SidePanel]: [page('module-filters', 'Filters', [filterPanel('module-filter-panel', 'Filter the module')])],\n    },\n    displayName: 'Data module page',\n    description: 'Module level: fits the application layout content slot and offers a body for one feature.',\n};\n\n/**\n * Feature level: fits the module page's `body` slot.\n *\n * A feature is where actions belong - a module is a grouping and a slice is one behavior, and the feature\n * in between is what a user thinks of as \"the screen with the buttons on it\". It offers a primary region\n * for the slice and a secondary one for the live view of what that slice is doing.\n */\nexport const dataFeatureSectionTemplate: ScreenTemplate = {\n    name: 'DataFeatureSection',\n    fitsSlot: TemplateSlotName.Body,\n    slots: [{ name: TemplateSlotName.Toolbar }, { name: TemplateSlotName.Primary }, { name: TemplateSlotName.Secondary }],\n    content: {\n        [TemplateSlotName.Toolbar]: [\n            toolbar('feature-toolbar', [\n                toolbarButton('feature-new', 'Register an invoice', 'pi pi-plus', 'New'),\n                toolbarButton('feature-adjust', 'Record an adjustment', 'pi pi-pencil', 'Adjust'),\n                toolbarSeparator('feature-separator'),\n                toolbarButton('feature-export', 'Export the feature data', 'pi pi-download'),\n            ]),\n        ],\n        [TemplateSlotName.Secondary]: [\n            page('feature-live', 'In flight', [\n                observableDataTable('feature-live-table', SampleBindingName.InvoicesInFlight, invoiceTableOptions, invoiceColumns),\n            ]),\n        ],\n    },\n    displayName: 'Data feature section',\n    description: 'Feature level: fits a module page body slot, brings the action toolbar and a live view.',\n};\n\n/**\n * Slice level: fits the feature section's `primary` slot.\n *\n * The end of the chain, and deliberately the thinnest thing in it. A slice is one behavior, and in a\n * Cratis application that behavior is one command - so its surface is a header saying what the command is\n * and whether it is wired, and the action that summons it. The capture itself happens in the `CommandDialog`\n * dialog template, which is why this template has no form on it and does not need one.\n */\nexport const commandSliceSectionTemplate: ScreenTemplate = {\n    name: 'CommandSliceSection',\n    fitsSlot: TemplateSlotName.Primary,\n    slots: [{ name: TemplateSlotName.Header }, { name: TemplateSlotName.Actions }],\n    content: {\n        [TemplateSlotName.Header]: [\n            arcPageHeader('slice-header', {\n                title: 'Record an adjustment',\n                subtitle: 'One behavior, one command, one button',\n                section: 'Adjustments',\n                command: SampleBindingName.RecordAdjustment,\n            }),\n        ],\n        [TemplateSlotName.Actions]: [\n            toolbar('slice-actions', [\n                toolbarButton('slice-record', 'Record an adjustment', 'pi pi-check', 'Record'),\n                toolbarButton('slice-cancel', 'Leave the invoice as it is', 'pi pi-times', 'Cancel'),\n            ]),\n        ],\n    },\n    displayName: 'Command slice section',\n    description: 'Slice level: fits a feature section primary slot and hosts one command behavior.',\n};\n\n/** The chain, outermost first - what a spec walks to prove `fitsSlot` resolves at every level. */\nexport const nestingChainTemplates: ScreenTemplate[] = [dataModulePageTemplate, dataFeatureSectionTemplate, commandSliceSectionTemplate];\n"],"names":["dataModulePageTemplate","name","fitsSlot","SlotName","Content","slots","TemplateSlotName","Header","Body","SidePanel","content","arcPageHeader","title","subtitle","section","page","filterPanel","displayName","description","dataFeatureSectionTemplate","Toolbar","Primary","Secondary","toolbar","toolbarButton","toolbarSeparator","observableDataTable","SampleBindingName","InvoicesInFlight","invoiceTableOptions","invoiceColumns","commandSliceSectionTemplate","Actions","command","RecordAdjustment","nestingChainTemplates"],"mappings":";;;;;;;;AAAA;AACA;AASA;;;;;;;;;;;;;;;;;;;;;;;UA0BaA,sBAAAA,GAAyC;IAClDC,IAAAA,EAAM,gBAAA;AACNC,IAAAA,QAAAA,EAAUC,iCAASC,OAAO;IAC1BC,KAAAA,EAAO;AAAC,QAAA;AAAEJ,YAAAA,IAAAA,EAAMK,yCAAiBC;AAAO,SAAA;AAAG,QAAA;AAAEN,YAAAA,IAAAA,EAAMK,yCAAiBE;AAAK,SAAA;AAAG,QAAA;AAAEP,YAAAA,IAAAA,EAAMK,yCAAiBG;AAAU;AAAE,KAAA;IACjHC,OAAAA,EAAS;QACL,CAACJ,wCAAAA,CAAiBC,MAAM,GAAG;AACvBI,YAAAA,sBAAAA,CAAc,eAAA,EAAiB;gBAC3BC,KAAAA,EAAO,SAAA;gBACPC,QAAAA,EAAU,oCAAA;gBACVC,OAAAA,EAAS;AACb,aAAA;AACH,SAAA;QACD,CAACR,wCAAAA,CAAiBG,SAAS,GAAG;AAACM,YAAAA,aAAAA,CAAK,kBAAkB,SAAA,EAAW;AAACC,gBAAAA,0BAAAA,CAAY,qBAAA,EAAuB,mBAAA;AAAqB,aAAA;AAAE;AAChI,KAAA;IACAC,WAAAA,EAAa,kBAAA;IACbC,WAAAA,EAAa;AACjB;AAEA;;;;;;UAOaC,0BAAAA,GAA6C;IACtDlB,IAAAA,EAAM,oBAAA;AACNC,IAAAA,QAAAA,EAAUI,yCAAiBE,IAAI;IAC/BH,KAAAA,EAAO;AAAC,QAAA;AAAEJ,YAAAA,IAAAA,EAAMK,yCAAiBc;AAAQ,SAAA;AAAG,QAAA;AAAEnB,YAAAA,IAAAA,EAAMK,yCAAiBe;AAAQ,SAAA;AAAG,QAAA;AAAEpB,YAAAA,IAAAA,EAAMK,yCAAiBgB;AAAU;AAAE,KAAA;IACrHZ,OAAAA,EAAS;QACL,CAACJ,wCAAAA,CAAiBc,OAAO,GAAG;AACxBG,YAAAA,gBAAAA,CAAQ,iBAAA,EAAmB;gBACvBC,sBAAAA,CAAc,aAAA,EAAe,uBAAuB,YAAA,EAAc,KAAA,CAAA;gBAClEA,sBAAAA,CAAc,gBAAA,EAAkB,wBAAwB,cAAA,EAAgB,QAAA,CAAA;gBACxEC,yBAAAA,CAAiB,mBAAA,CAAA;AACjBD,gBAAAA,sBAAAA,CAAc,kBAAkB,yBAAA,EAA2B,gBAAA;AAC9D,aAAA;AACJ,SAAA;QACD,CAAClB,wCAAAA,CAAiBgB,SAAS,GAAG;AAC1BP,YAAAA,aAAAA,CAAK,gBAAgB,WAAA,EAAa;AAC9BW,gBAAAA,gCAAAA,CAAoB,oBAAA,EAAsBC,mCAAAA,CAAkBC,gBAAgB,EAAEC,gCAAAA,EAAqBC,2BAAAA;AACtG,aAAA;AACJ;AACL,KAAA;IACAb,WAAAA,EAAa,sBAAA;IACbC,WAAAA,EAAa;AACjB;AAEA;;;;;;;UAQaa,2BAAAA,GAA8C;IACvD9B,IAAAA,EAAM,qBAAA;AACNC,IAAAA,QAAAA,EAAUI,yCAAiBe,OAAO;IAClChB,KAAAA,EAAO;AAAC,QAAA;AAAEJ,YAAAA,IAAAA,EAAMK,yCAAiBC;AAAO,SAAA;AAAG,QAAA;AAAEN,YAAAA,IAAAA,EAAMK,yCAAiB0B;AAAQ;AAAE,KAAA;IAC9EtB,OAAAA,EAAS;QACL,CAACJ,wCAAAA,CAAiBC,MAAM,GAAG;AACvBI,YAAAA,sBAAAA,CAAc,cAAA,EAAgB;gBAC1BC,KAAAA,EAAO,sBAAA;gBACPC,QAAAA,EAAU,uCAAA;gBACVC,OAAAA,EAAS,aAAA;AACTmB,gBAAAA,OAAAA,EAASN,oCAAkBO;AAC/B,aAAA;AACH,SAAA;QACD,CAAC5B,wCAAAA,CAAiB0B,OAAO,GAAG;AACxBT,YAAAA,gBAAAA,CAAQ,eAAA,EAAiB;gBACrBC,sBAAAA,CAAc,cAAA,EAAgB,wBAAwB,aAAA,EAAe,QAAA,CAAA;gBACrEA,sBAAAA,CAAc,cAAA,EAAgB,8BAA8B,aAAA,EAAe,QAAA;AAC9E,aAAA;AACJ;AACL,KAAA;IACAP,WAAAA,EAAa,uBAAA;IACbC,WAAAA,EAAa;AACjB;AAEA,mGACO,MAAMiB,qBAAAA,GAA0C;AAACnC,IAAAA,sBAAAA;AAAwBmB,IAAAA,0BAAAA;AAA4BY,IAAAA;;;;;;;;"}