@cratis/scene.blueprint.components 0.1.0

package/dist/esm/templates/listTemplates.js

@@ -0,0 +1,182 @@
+import { WidthSizeClass } from '@cratis/scene.model';
+import { TemplateSlotName, SlotName, column, slotLeaf, row } from '@cratis/scene.blueprint.default';
+import { dataPage, observableDataTable, invoiceTableOptions, invoiceColumns } from './dataElements.js';
+import { objectNavigationalBar, objectContentEditor, timeMachine } from './editorElements.js';
+import { arcPageHeader, toolbar, toolbarButton, toolbarSeparator, toolbarGroup, page } from './elements.js';
+import { SampleBindingName } from './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: SlotName.Content,
+    slots: [
+        {
+            name: TemplateSlotName.Header
+        },
+        {
+            name: TemplateSlotName.Body
+        }
+    ],
+    content: {
+        [TemplateSlotName.Header]: [
+            arcPageHeader('data-list-header', {
+                title: 'Invoices',
+                subtitle: 'Every invoice, filterable and paged against the server',
+                section: 'Billing',
+                query: SampleBindingName.AllInvoices
+            }, [
+                toolbar('data-list-actions', [
+                    toolbarButton('data-list-new', 'Register an invoice', 'pi pi-plus', 'New'),
+                    toolbarButton('data-list-refresh', 'Refresh', 'pi pi-refresh'),
+                    toolbarSeparator('data-list-separator'),
+                    toolbarGroup('data-list-export', [
+                        toolbarButton('data-list-download', 'Download as CSV', 'pi pi-download'),
+                        toolbarButton('data-list-print', 'Print', 'pi pi-print')
+                    ])
+                ])
+            ])
+        ],
+        [TemplateSlotName.Body]: [
+            dataPage('data-list-body', SampleBindingName.AllInvoices, invoiceTableOptions, 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: SlotName.Content,
+    slots: [
+        {
+            name: TemplateSlotName.Header
+        },
+        {
+            name: TemplateSlotName.Body
+        }
+    ],
+    content: {
+        [TemplateSlotName.Header]: [
+            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.InvoicesInFlight
+            })
+        ],
+        [TemplateSlotName.Body]: [
+            page('observable-list-body', 'In flight', [
+                observableDataTable('observable-list-table', SampleBindingName.InvoicesInFlight, invoiceTableOptions, 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: SlotName.Content,
+    slots: [
+        {
+            name: TemplateSlotName.Header
+        },
+        {
+            name: TemplateSlotName.Body
+        },
+        {
+            name: TemplateSlotName.SidePanel
+        }
+    ],
+    arrangement: {
+        root: column([
+            slotLeaf(TemplateSlotName.Header),
+            row([
+                slotLeaf(TemplateSlotName.Body, {
+                    grow: 2
+                }),
+                slotLeaf(TemplateSlotName.SidePanel, {
+                    grow: 1
+                })
+            ], 16)
+        ]),
+        overrides: [
+            {
+                width: WidthSizeClass.Compact,
+                root: column([
+                    slotLeaf(TemplateSlotName.Header),
+                    slotLeaf(TemplateSlotName.Body),
+                    slotLeaf(TemplateSlotName.SidePanel)
+                ], 16)
+            }
+        ]
+    },
+    content: {
+        [TemplateSlotName.Header]: [
+            arcPageHeader('list-detail-header', {
+                title: 'Invoices',
+                subtitle: 'The list, with the selected invoice beside it',
+                section: 'Billing',
+                query: SampleBindingName.AllInvoices
+            })
+        ],
+        [TemplateSlotName.Body]: [
+            dataPage('list-detail-body', SampleBindingName.AllInvoices, invoiceTableOptions, invoiceColumns)
+        ],
+        [TemplateSlotName.SidePanel]: [
+            page('list-detail-panel', 'Selected invoice', [
+                objectNavigationalBar('list-detail-trail'),
+                objectContentEditor('list-detail-document', false),
+                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
+];
+
+export { dataListPageTemplate, dataListWithDetailPageTemplate, listTemplates, observableDataListPageTemplate };
+//# sourceMappingURL=listTemplates.js.map

package/dist/esm/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,SAASC,OAAO;IAC1BC,KAAAA,EAAO;AAAC,QAAA;AAAEJ,YAAAA,IAAAA,EAAMK,iBAAiBC;AAAO,SAAA;AAAG,QAAA;AAAEN,YAAAA,IAAAA,EAAMK,iBAAiBE;AAAK;AAAE,KAAA;IAC3EC,OAAAA,EAAS;QACL,CAACH,gBAAAA,CAAiBC,MAAM,GAAG;AACvBG,YAAAA,aAAAA,CACI,kBAAA,EACA;gBAAEC,KAAAA,EAAO,UAAA;gBAAYC,QAAAA,EAAU,wDAAA;gBAA0DC,OAAAA,EAAS,SAAA;AAAWC,gBAAAA,KAAAA,EAAOC,kBAAkBC;aAAY,EAClJ;AACIC,gBAAAA,OAAAA,CAAQ,mBAAA,EAAqB;oBACzBC,aAAAA,CAAc,eAAA,EAAiB,uBAAuB,YAAA,EAAc,KAAA,CAAA;AACpEA,oBAAAA,aAAAA,CAAc,qBAAqB,SAAA,EAAW,eAAA,CAAA;oBAC9CC,gBAAAA,CAAiB,qBAAA,CAAA;AACjBC,oBAAAA,YAAAA,CAAa,kBAAA,EAAoB;AAC7BF,wBAAAA,aAAAA,CAAc,sBAAsB,iBAAA,EAAmB,gBAAA,CAAA;AACvDA,wBAAAA,aAAAA,CAAc,mBAAmB,OAAA,EAAS,aAAA;AAC7C,qBAAA;AACJ,iBAAA;AACJ,aAAA;AAER,SAAA;QACD,CAACZ,gBAAAA,CAAiBE,IAAI,GAAG;AAACa,YAAAA,QAAAA,CAAS,gBAAA,EAAkBN,iBAAAA,CAAkBC,WAAW,EAAEM,mBAAAA,EAAqBC,cAAAA;AAAgB;AAC7H,KAAA;IACAC,WAAAA,EAAa,gBAAA;IACbC,WAAAA,EAAa;AACjB;AAEA;;;;;;;;UASaC,8BAAAA,GAAiD;IAC1DzB,IAAAA,EAAM,wBAAA;AACNC,IAAAA,QAAAA,EAAUC,SAASC,OAAO;IAC1BC,KAAAA,EAAO;AAAC,QAAA;AAAEJ,YAAAA,IAAAA,EAAMK,iBAAiBC;AAAO,SAAA;AAAG,QAAA;AAAEN,YAAAA,IAAAA,EAAMK,iBAAiBE;AAAK;AAAE,KAAA;IAC3EC,OAAAA,EAAS;QACL,CAACH,gBAAAA,CAAiBC,MAAM,GAAG;AACvBG,YAAAA,aAAAA,CAAc,wBAAA,EAA0B;gBACpCC,KAAAA,EAAO,oBAAA;gBACPC,QAAAA,EAAU,4FAAA;gBACVC,OAAAA,EAAS,SAAA;AACTC,gBAAAA,KAAAA,EAAOC,kBAAkBY;AAC7B,aAAA;AACH,SAAA;QACD,CAACrB,gBAAAA,CAAiBE,IAAI,GAAG;AACrBoB,YAAAA,IAAAA,CAAK,wBAAwB,WAAA,EAAa;AACtCC,gBAAAA,mBAAAA,CAAoB,uBAAA,EAAyBd,iBAAAA,CAAkBY,gBAAgB,EAAEL,mBAAAA,EAAqBC,cAAAA;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,SAASC,OAAO;IAC1BC,KAAAA,EAAO;AAAC,QAAA;AAAEJ,YAAAA,IAAAA,EAAMK,iBAAiBC;AAAO,SAAA;AAAG,QAAA;AAAEN,YAAAA,IAAAA,EAAMK,iBAAiBE;AAAK,SAAA;AAAG,QAAA;AAAEP,YAAAA,IAAAA,EAAMK,iBAAiByB;AAAU;AAAE,KAAA;IACjHC,WAAAA,EAAa;AACTC,QAAAA,IAAAA,EAAMC,MAAAA,CAAO;AAACC,YAAAA,QAAAA,CAAS7B,iBAAiBC,MAAM,CAAA;YAAG6B,GAAAA,CAAI;gBAACD,QAAAA,CAAS7B,gBAAAA,CAAiBE,IAAI,EAAE;oBAAE6B,IAAAA,EAAM;AAAE,iBAAA,CAAA;gBAAIF,QAAAA,CAAS7B,gBAAAA,CAAiByB,SAAS,EAAE;oBAAEM,IAAAA,EAAM;AAAE,iBAAA;aAAG,EAAE,EAAA;AAAI,SAAA,CAAA;QAC5JC,SAAAA,EAAW;AACP,YAAA;AACIC,gBAAAA,KAAAA,EAAOC,eAAeC,OAAO;AAC7BR,gBAAAA,IAAAA,EAAMC,MAAAA,CAAO;AAACC,oBAAAA,QAAAA,CAAS7B,iBAAiBC,MAAM,CAAA;AAAG4B,oBAAAA,QAAAA,CAAS7B,iBAAiBE,IAAI,CAAA;AAAG2B,oBAAAA,QAAAA,CAAS7B,iBAAiByB,SAAS;iBAAE,EAAE,EAAA;AAC7H;AACH;AACL,KAAA;IACAtB,OAAAA,EAAS;QACL,CAACH,gBAAAA,CAAiBC,MAAM,GAAG;AACvBG,YAAAA,aAAAA,CAAc,oBAAA,EAAsB;gBAChCC,KAAAA,EAAO,UAAA;gBACPC,QAAAA,EAAU,+CAAA;gBACVC,OAAAA,EAAS,SAAA;AACTC,gBAAAA,KAAAA,EAAOC,kBAAkBC;AAC7B,aAAA;AACH,SAAA;QACD,CAACV,gBAAAA,CAAiBE,IAAI,GAAG;AAACa,YAAAA,QAAAA,CAAS,kBAAA,EAAoBN,iBAAAA,CAAkBC,WAAW,EAAEM,mBAAAA,EAAqBC,cAAAA;AAAgB,SAAA;QAC3H,CAACjB,gBAAAA,CAAiByB,SAAS,GAAG;AAC1BH,YAAAA,IAAAA,CAAK,qBAAqB,kBAAA,EAAoB;gBAC1Cc,qBAAAA,CAAsB,mBAAA,CAAA;AACtBC,gBAAAA,mBAAAA,CAAoB,sBAAA,EAAwB,KAAA,CAAA;gBAC5CC,WAAAA,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/esm/templates/nesting.d.ts

@@ -0,0 +1,6 @@
+import { ScreenTemplate } from '@cratis/scene.model';
+export declare const dataModulePageTemplate: ScreenTemplate;
+export declare const dataFeatureSectionTemplate: ScreenTemplate;
+export declare const commandSliceSectionTemplate: ScreenTemplate;
+export declare const nestingChainTemplates: ScreenTemplate[];
+//# sourceMappingURL=nesting.d.ts.map

package/dist/esm/templates/nesting.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"nesting.d.ts","sourceRoot":"","sources":["../../../templates/nesting.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,cAAc,EAAE,MAAM,qBAAqB,CAAC;AAiCrD,eAAO,MAAM,sBAAsB,EAAE,cAgBpC,CAAC;AASF,eAAO,MAAM,0BAA0B,EAAE,cAqBxC,CAAC;AAUF,eAAO,MAAM,2BAA2B,EAAE,cAsBzC,CAAC;AAGF,eAAO,MAAM,qBAAqB,EAAE,cAAc,EAAsF,CAAC"}

package/dist/esm/templates/nesting.js

@@ -0,0 +1,145 @@
+import { TemplateSlotName, SlotName } from '@cratis/scene.blueprint.default';
+import { observableDataTable, invoiceTableOptions, invoiceColumns } from './dataElements.js';
+import { filterPanel } from './editorElements.js';
+import { page, arcPageHeader, toolbar, toolbarButton, toolbarSeparator } from './elements.js';
+import { SampleBindingName } from './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: SlotName.Content,
+    slots: [
+        {
+            name: TemplateSlotName.Header
+        },
+        {
+            name: TemplateSlotName.Body
+        },
+        {
+            name: TemplateSlotName.SidePanel
+        }
+    ],
+    content: {
+        [TemplateSlotName.Header]: [
+            arcPageHeader('module-header', {
+                title: 'Billing',
+                subtitle: 'Everything the billing module owns',
+                section: 'Operations'
+            })
+        ],
+        [TemplateSlotName.SidePanel]: [
+            page('module-filters', 'Filters', [
+                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: TemplateSlotName.Body,
+    slots: [
+        {
+            name: TemplateSlotName.Toolbar
+        },
+        {
+            name: TemplateSlotName.Primary
+        },
+        {
+            name: TemplateSlotName.Secondary
+        }
+    ],
+    content: {
+        [TemplateSlotName.Toolbar]: [
+            toolbar('feature-toolbar', [
+                toolbarButton('feature-new', 'Register an invoice', 'pi pi-plus', 'New'),
+                toolbarButton('feature-adjust', 'Record an adjustment', 'pi pi-pencil', 'Adjust'),
+                toolbarSeparator('feature-separator'),
+                toolbarButton('feature-export', 'Export the feature data', 'pi pi-download')
+            ])
+        ],
+        [TemplateSlotName.Secondary]: [
+            page('feature-live', 'In flight', [
+                observableDataTable('feature-live-table', SampleBindingName.InvoicesInFlight, invoiceTableOptions, 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: TemplateSlotName.Primary,
+    slots: [
+        {
+            name: TemplateSlotName.Header
+        },
+        {
+            name: TemplateSlotName.Actions
+        }
+    ],
+    content: {
+        [TemplateSlotName.Header]: [
+            arcPageHeader('slice-header', {
+                title: 'Record an adjustment',
+                subtitle: 'One behavior, one command, one button',
+                section: 'Adjustments',
+                command: SampleBindingName.RecordAdjustment
+            })
+        ],
+        [TemplateSlotName.Actions]: [
+            toolbar('slice-actions', [
+                toolbarButton('slice-record', 'Record an adjustment', 'pi pi-check', 'Record'),
+                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
+];
+
+export { commandSliceSectionTemplate, dataFeatureSectionTemplate, dataModulePageTemplate, nestingChainTemplates };
+//# sourceMappingURL=nesting.js.map

package/dist/esm/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,SAASC,OAAO;IAC1BC,KAAAA,EAAO;AAAC,QAAA;AAAEJ,YAAAA,IAAAA,EAAMK,iBAAiBC;AAAO,SAAA;AAAG,QAAA;AAAEN,YAAAA,IAAAA,EAAMK,iBAAiBE;AAAK,SAAA;AAAG,QAAA;AAAEP,YAAAA,IAAAA,EAAMK,iBAAiBG;AAAU;AAAE,KAAA;IACjHC,OAAAA,EAAS;QACL,CAACJ,gBAAAA,CAAiBC,MAAM,GAAG;AACvBI,YAAAA,aAAAA,CAAc,eAAA,EAAiB;gBAC3BC,KAAAA,EAAO,SAAA;gBACPC,QAAAA,EAAU,oCAAA;gBACVC,OAAAA,EAAS;AACb,aAAA;AACH,SAAA;QACD,CAACR,gBAAAA,CAAiBG,SAAS,GAAG;AAACM,YAAAA,IAAAA,CAAK,kBAAkB,SAAA,EAAW;AAACC,gBAAAA,WAAAA,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,iBAAiBE,IAAI;IAC/BH,KAAAA,EAAO;AAAC,QAAA;AAAEJ,YAAAA,IAAAA,EAAMK,iBAAiBc;AAAQ,SAAA;AAAG,QAAA;AAAEnB,YAAAA,IAAAA,EAAMK,iBAAiBe;AAAQ,SAAA;AAAG,QAAA;AAAEpB,YAAAA,IAAAA,EAAMK,iBAAiBgB;AAAU;AAAE,KAAA;IACrHZ,OAAAA,EAAS;QACL,CAACJ,gBAAAA,CAAiBc,OAAO,GAAG;AACxBG,YAAAA,OAAAA,CAAQ,iBAAA,EAAmB;gBACvBC,aAAAA,CAAc,aAAA,EAAe,uBAAuB,YAAA,EAAc,KAAA,CAAA;gBAClEA,aAAAA,CAAc,gBAAA,EAAkB,wBAAwB,cAAA,EAAgB,QAAA,CAAA;gBACxEC,gBAAAA,CAAiB,mBAAA,CAAA;AACjBD,gBAAAA,aAAAA,CAAc,kBAAkB,yBAAA,EAA2B,gBAAA;AAC9D,aAAA;AACJ,SAAA;QACD,CAAClB,gBAAAA,CAAiBgB,SAAS,GAAG;AAC1BP,YAAAA,IAAAA,CAAK,gBAAgB,WAAA,EAAa;AAC9BW,gBAAAA,mBAAAA,CAAoB,oBAAA,EAAsBC,iBAAAA,CAAkBC,gBAAgB,EAAEC,mBAAAA,EAAqBC,cAAAA;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,iBAAiBe,OAAO;IAClChB,KAAAA,EAAO;AAAC,QAAA;AAAEJ,YAAAA,IAAAA,EAAMK,iBAAiBC;AAAO,SAAA;AAAG,QAAA;AAAEN,YAAAA,IAAAA,EAAMK,iBAAiB0B;AAAQ;AAAE,KAAA;IAC9EtB,OAAAA,EAAS;QACL,CAACJ,gBAAAA,CAAiBC,MAAM,GAAG;AACvBI,YAAAA,aAAAA,CAAc,cAAA,EAAgB;gBAC1BC,KAAAA,EAAO,sBAAA;gBACPC,QAAAA,EAAU,uCAAA;gBACVC,OAAAA,EAAS,aAAA;AACTmB,gBAAAA,OAAAA,EAASN,kBAAkBO;AAC/B,aAAA;AACH,SAAA;QACD,CAAC5B,gBAAAA,CAAiB0B,OAAO,GAAG;AACxBT,YAAAA,OAAAA,CAAQ,eAAA,EAAiB;gBACrBC,aAAAA,CAAc,cAAA,EAAgB,wBAAwB,aAAA,EAAe,QAAA,CAAA;gBACrEA,aAAAA,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;;;;;"}

package/dist/esm/templates/sampleData.d.ts

@@ -0,0 +1,10 @@
+export declare const invoiceSchema: Record<string, unknown>;
+export declare const invoiceDocument: Record<string, unknown>;
+export declare const invoiceNavigationPath: string[];
+export declare const invoiceVersions: Record<string, unknown>[];
+export declare const invoiceFilters: Record<string, unknown>[];
+export declare const statusOptions: {
+    label: string;
+    value: string;
+}[];
+//# sourceMappingURL=sampleData.d.ts.map

package/dist/esm/templates/sampleData.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sampleData.d.ts","sourceRoot":"","sources":["../../../templates/sampleData.ts"],"names":[],"mappings":"AAqBA,eAAO,MAAM,aAAa,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAUjD,CAAC;AAGF,eAAO,MAAM,eAAe,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAMnD,CAAC;AAGF,eAAO,MAAM,qBAAqB,EAAE,MAAM,EAA0B,CAAC;AASrE,eAAO,MAAM,eAAe,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAIpD,CAAC;AAGF,eAAO,MAAM,cAAc,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAcnD,CAAC;AAGF,eAAO,MAAM,aAAa,EAAE;IAAE,KAAK,EAAE,MAAM,CAAC;IAAC,KAAK,EAAE,MAAM,CAAA;CAAE,EAI3D,CAAC"}

package/dist/esm/templates/sampleData.js

@@ -0,0 +1,134 @@
+// Copyright (c) Cratis. All rights reserved.
+// Licensed under the MIT license. See LICENSE file in the project root for full license information.
+/**
+ * The seeded content the Arc-free composites in this package's templates render.
+ *
+ * There is a real split running through this blueprint, and it is worth naming rather than hiding. Most of
+ * `@cratis/components` is Arc-bound: a data page, a table, a command form and a command dialog all need a
+ * registered proxy and a live backend before they show anything, so at design time they are placeholders,
+ * and that is correct.
+ *
+ * The editors are not. A schema editor, a document editor, a navigational bar and a time machine all take
+ * their content from the property bag, so a template that seeds them renders as a working page with no
+ * backend at all. That is why the editor templates carry this data: it makes two of this package's pages
+ * genuinely usable in a preview, rather than eight pages of dashed boxes.
+ *
+ * The shape is an invoice throughout, matching the query and command names the other templates bind to, so
+ * the whole package reads as one small application rather than eight unrelated demonstrations.
+ */ /** A JSON schema in the shape Chronicle emits for an event type - what `schemaEditor` edits. */ const invoiceSchema = {
+    title: 'InvoiceRegistered',
+    type: 'object',
+    properties: {
+        number: {
+            type: 'string',
+            description: 'The invoice number as printed on the document.'
+        },
+        customer: {
+            type: 'string',
+            description: 'The customer the invoice is addressed to.'
+        },
+        issued: {
+            type: 'string',
+            format: 'date-time',
+            description: 'When the invoice was issued.'
+        },
+        amount: {
+            type: 'number',
+            description: 'The gross amount, in the invoice currency.'
+        },
+        currency: {
+            type: 'string',
+            description: 'The ISO currency code.'
+        }
+    }
+};
+/** One invoice as a plain document - what `objectContentEditor` renders against {@link invoiceSchema}. */ const invoiceDocument = {
+    number: 'INV-2043',
+    customer: 'Northwind Traders',
+    issued: '2026-01-05T09:30:00Z',
+    amount: 4200,
+    currency: 'USD'
+};
+/** Where in the document the navigational bar currently is. */ const invoiceNavigationPath = [
+    'lines',
+    'shipping'
+];
+/**
+ * Successive versions of the invoice, for the time machine.
+ *
+ * Every entry has an id, a label and a parseable timestamp, because the adapter drops any that does not -
+ * a version invented at the epoch would not be a slightly wrong entry, it would silently reorder every
+ * real one around it.
+ */ const invoiceVersions = [
+    {
+        id: 'v3',
+        label: 'Adjustment recorded',
+        timestamp: '2026-01-12T14:05:00Z',
+        content: 'Amount reduced by 120.00 - damaged goods'
+    },
+    {
+        id: 'v2',
+        label: 'Approved',
+        timestamp: '2026-01-07T08:15:00Z',
+        content: 'Approved by Amelia Nyquist'
+    },
+    {
+        id: 'v1',
+        label: 'Registered',
+        timestamp: '2026-01-05T09:30:00Z',
+        content: 'Registered from the supplier portal'
+    }
+];
+/** The filters the list templates offer, in the shape `filterPanel` reads. */ const invoiceFilters = [
+    {
+        key: 'status',
+        label: 'Status',
+        type: 'string',
+        multi: true,
+        options: [
+            {
+                key: 'draft',
+                label: 'Draft',
+                count: 12
+            },
+            {
+                key: 'approved',
+                label: 'Approved',
+                count: 44
+            },
+            {
+                key: 'paid',
+                label: 'Paid',
+                count: 108
+            }
+        ]
+    },
+    {
+        key: 'amount',
+        label: 'Amount',
+        type: 'number',
+        buckets: 4
+    },
+    {
+        key: 'issued',
+        label: 'Issued',
+        type: 'date'
+    }
+];
+/** The status choices a command form's dropdown offers. */ const statusOptions = [
+    {
+        label: 'Draft',
+        value: 'draft'
+    },
+    {
+        label: 'Approved',
+        value: 'approved'
+    },
+    {
+        label: 'Paid',
+        value: 'paid'
+    }
+];
+
+export { invoiceDocument, invoiceFilters, invoiceNavigationPath, invoiceSchema, invoiceVersions, statusOptions };
+//# sourceMappingURL=sampleData.js.map

package/dist/esm/templates/sampleData.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"sampleData.js","sources":["../../../templates/sampleData.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\n/**\n * The seeded content the Arc-free composites in this package's templates render.\n *\n * There is a real split running through this blueprint, and it is worth naming rather than hiding. Most of\n * `@cratis/components` is Arc-bound: a data page, a table, a command form and a command dialog all need a\n * registered proxy and a live backend before they show anything, so at design time they are placeholders,\n * and that is correct.\n *\n * The editors are not. A schema editor, a document editor, a navigational bar and a time machine all take\n * their content from the property bag, so a template that seeds them renders as a working page with no\n * backend at all. That is why the editor templates carry this data: it makes two of this package's pages\n * genuinely usable in a preview, rather than eight pages of dashed boxes.\n *\n * The shape is an invoice throughout, matching the query and command names the other templates bind to, so\n * the whole package reads as one small application rather than eight unrelated demonstrations.\n */\n\n/** A JSON schema in the shape Chronicle emits for an event type - what `schemaEditor` edits. */\nexport const invoiceSchema: Record<string, unknown> = {\n    title: 'InvoiceRegistered',\n    type: 'object',\n    properties: {\n        number: { type: 'string', description: 'The invoice number as printed on the document.' },\n        customer: { type: 'string', description: 'The customer the invoice is addressed to.' },\n        issued: { type: 'string', format: 'date-time', description: 'When the invoice was issued.' },\n        amount: { type: 'number', description: 'The gross amount, in the invoice currency.' },\n        currency: { type: 'string', description: 'The ISO currency code.' },\n    },\n};\n\n/** One invoice as a plain document - what `objectContentEditor` renders against {@link invoiceSchema}. */\nexport const invoiceDocument: Record<string, unknown> = {\n    number: 'INV-2043',\n    customer: 'Northwind Traders',\n    issued: '2026-01-05T09:30:00Z',\n    amount: 4200,\n    currency: 'USD',\n};\n\n/** Where in the document the navigational bar currently is. */\nexport const invoiceNavigationPath: string[] = ['lines', 'shipping'];\n\n/**\n * Successive versions of the invoice, for the time machine.\n *\n * Every entry has an id, a label and a parseable timestamp, because the adapter drops any that does not -\n * a version invented at the epoch would not be a slightly wrong entry, it would silently reorder every\n * real one around it.\n */\nexport const invoiceVersions: Record<string, unknown>[] = [\n    { id: 'v3', label: 'Adjustment recorded', timestamp: '2026-01-12T14:05:00Z', content: 'Amount reduced by 120.00 - damaged goods' },\n    { id: 'v2', label: 'Approved', timestamp: '2026-01-07T08:15:00Z', content: 'Approved by Amelia Nyquist' },\n    { id: 'v1', label: 'Registered', timestamp: '2026-01-05T09:30:00Z', content: 'Registered from the supplier portal' },\n];\n\n/** The filters the list templates offer, in the shape `filterPanel` reads. */\nexport const invoiceFilters: Record<string, unknown>[] = [\n    {\n        key: 'status',\n        label: 'Status',\n        type: 'string',\n        multi: true,\n        options: [\n            { key: 'draft', label: 'Draft', count: 12 },\n            { key: 'approved', label: 'Approved', count: 44 },\n            { key: 'paid', label: 'Paid', count: 108 },\n        ],\n    },\n    { key: 'amount', label: 'Amount', type: 'number', buckets: 4 },\n    { key: 'issued', label: 'Issued', type: 'date' },\n];\n\n/** The status choices a command form's dropdown offers. */\nexport const statusOptions: { label: string; value: string }[] = [\n    { label: 'Draft', value: 'draft' },\n    { label: 'Approved', value: 'approved' },\n    { label: 'Paid', value: 'paid' },\n];\n"],"names":["invoiceSchema","title","type","properties","number","description","customer","issued","format","amount","currency","invoiceDocument","invoiceNavigationPath","invoiceVersions","id","label","timestamp","content","invoiceFilters","key","multi","options","count","buckets","statusOptions","value"],"mappings":"AAAA;AACA;AAEA;;;;;;;;;;;;;;;AAeC,qGAGM,MAAMA,aAAAA,GAAyC;IAClDC,KAAAA,EAAO,mBAAA;IACPC,IAAAA,EAAM,QAAA;IACNC,UAAAA,EAAY;QACRC,MAAAA,EAAQ;YAAEF,IAAAA,EAAM,QAAA;YAAUG,WAAAA,EAAa;AAAiD,SAAA;QACxFC,QAAAA,EAAU;YAAEJ,IAAAA,EAAM,QAAA;YAAUG,WAAAA,EAAa;AAA4C,SAAA;QACrFE,MAAAA,EAAQ;YAAEL,IAAAA,EAAM,QAAA;YAAUM,MAAAA,EAAQ,WAAA;YAAaH,WAAAA,EAAa;AAA+B,SAAA;QAC3FI,MAAAA,EAAQ;YAAEP,IAAAA,EAAM,QAAA;YAAUG,WAAAA,EAAa;AAA6C,SAAA;QACpFK,QAAAA,EAAU;YAAER,IAAAA,EAAM,QAAA;YAAUG,WAAAA,EAAa;AAAyB;AACtE;AACJ;AAEA,2GACO,MAAMM,eAAAA,GAA2C;IACpDP,MAAAA,EAAQ,UAAA;IACRE,QAAAA,EAAU,mBAAA;IACVC,MAAAA,EAAQ,sBAAA;IACRE,MAAAA,EAAQ,IAAA;IACRC,QAAAA,EAAU;AACd;AAEA,gEACO,MAAME,qBAAAA,GAAkC;AAAC,IAAA,OAAA;AAAS,IAAA;;AAEzD;;;;;;UAOaC,eAAAA,GAA6C;AACtD,IAAA;QAAEC,EAAAA,EAAI,IAAA;QAAMC,KAAAA,EAAO,qBAAA;QAAuBC,SAAAA,EAAW,sBAAA;QAAwBC,OAAAA,EAAS;AAA2C,KAAA;AACjI,IAAA;QAAEH,EAAAA,EAAI,IAAA;QAAMC,KAAAA,EAAO,UAAA;QAAYC,SAAAA,EAAW,sBAAA;QAAwBC,OAAAA,EAAS;AAA6B,KAAA;AACxG,IAAA;QAAEH,EAAAA,EAAI,IAAA;QAAMC,KAAAA,EAAO,YAAA;QAAcC,SAAAA,EAAW,sBAAA;QAAwBC,OAAAA,EAAS;AAAsC;;AAGvH,+EACO,MAAMC,cAAAA,GAA4C;AACrD,IAAA;QACIC,GAAAA,EAAK,QAAA;QACLJ,KAAAA,EAAO,QAAA;QACPb,IAAAA,EAAM,QAAA;QACNkB,KAAAA,EAAO,IAAA;QACPC,OAAAA,EAAS;AACL,YAAA;gBAAEF,GAAAA,EAAK,OAAA;gBAASJ,KAAAA,EAAO,OAAA;gBAASO,KAAAA,EAAO;AAAG,aAAA;AAC1C,YAAA;gBAAEH,GAAAA,EAAK,UAAA;gBAAYJ,KAAAA,EAAO,UAAA;gBAAYO,KAAAA,EAAO;AAAG,aAAA;AAChD,YAAA;gBAAEH,GAAAA,EAAK,MAAA;gBAAQJ,KAAAA,EAAO,MAAA;gBAAQO,KAAAA,EAAO;AAAI;AAC5C;AACL,KAAA;AACA,IAAA;QAAEH,GAAAA,EAAK,QAAA;QAAUJ,KAAAA,EAAO,QAAA;QAAUb,IAAAA,EAAM,QAAA;QAAUqB,OAAAA,EAAS;AAAE,KAAA;AAC7D,IAAA;QAAEJ,GAAAA,EAAK,QAAA;QAAUJ,KAAAA,EAAO,QAAA;QAAUb,IAAAA,EAAM;AAAO;;AAGnD,4DACO,MAAMsB,aAAAA,GAAoD;AAC7D,IAAA;QAAET,KAAAA,EAAO,OAAA;QAASU,KAAAA,EAAO;AAAQ,KAAA;AACjC,IAAA;QAAEV,KAAAA,EAAO,UAAA;QAAYU,KAAAA,EAAO;AAAW,KAAA;AACvC,IAAA;QAAEV,KAAAA,EAAO,MAAA;QAAQU,KAAAA,EAAO;AAAO;;;;;"}

package/dist/esm/templates/screenTemplates.d.ts

@@ -0,0 +1,4 @@
+import { ScreenTemplate } from '@cratis/scene.model';
+export declare const componentsScreenTemplates: ScreenTemplate[];
+export declare const componentsPageTemplates: ScreenTemplate[];
+//# sourceMappingURL=screenTemplates.d.ts.map

package/dist/esm/templates/screenTemplates.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"screenTemplates.d.ts","sourceRoot":"","sources":["../../../templates/screenTemplates.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,cAAc,EAAE,MAAM,qBAAqB,CAAC;AAcrD,eAAO,MAAM,yBAAyB,EAAE,cAAc,EAMrD,CAAC;AAWF,eAAO,MAAM,uBAAuB,EAAE,cAAc,EAAuF,CAAC"}

package/dist/esm/templates/screenTemplates.js

@@ -0,0 +1,38 @@
+import { commandTemplates } from './commandTemplates.js';
+import { editorTemplates } from './editorTemplates.js';
+import { listTemplates } from './listTemplates.js';
+import { nestingChainTemplates } from './nesting.js';
+import { workspaceTemplates } from './workspaceTemplates.js';
+
+// Copyright (c) Cratis. All rights reserved.
+// Licensed under the MIT license. See LICENSE file in the project root for full license information.
+/**
+ * The screen templates this blueprint provides.
+ *
+ * Eight whole pages that fill the application shell's `content` slot, plus the three-level chain that
+ * demonstrates how `fitsSlot` composes at module, feature and slice level. The list is what the manifest's
+ * `screenTemplates` names and what the bundle provides; `validatePackageBundle` proves the two agree.
+ */ const componentsScreenTemplates = [
+    ...listTemplates,
+    ...workspaceTemplates,
+    ...commandTemplates,
+    ...editorTemplates,
+    ...nestingChainTemplates
+];
+/**
+ * The eight templates that fill the application layout's own `content` slot directly.
+ *
+ * Kept apart from the nesting chain because `fitsSlot` is resolved against *the containers in scope*, and
+ * these two groups are never in scope together. Each of these is a whole page an application places on its
+ * own; the chain's three are one page assembled from three levels. Resolving them as one set would ask
+ * `resolveScreenTemplates` which of eight `body`-declaring templates the feature section belongs to, and it
+ * would rightly answer that it cannot tell.
+ */ const componentsPageTemplates = [
+    ...listTemplates,
+    ...workspaceTemplates,
+    ...commandTemplates,
+    ...editorTemplates
+];
+
+export { componentsPageTemplates, componentsScreenTemplates };
+//# sourceMappingURL=screenTemplates.js.map

package/dist/esm/templates/screenTemplates.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"screenTemplates.js","sources":["../../../templates/screenTemplates.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 { commandTemplates } from './commandTemplates';\nimport { editorTemplates } from './editorTemplates';\nimport { listTemplates } from './listTemplates';\nimport { nestingChainTemplates } from './nesting';\nimport { workspaceTemplates } from './workspaceTemplates';\n\n/**\n * The screen templates this blueprint provides.\n *\n * Eight whole pages that fill the application shell's `content` slot, plus the three-level chain that\n * demonstrates how `fitsSlot` composes at module, feature and slice level. The list is what the manifest's\n * `screenTemplates` names and what the bundle provides; `validatePackageBundle` proves the two agree.\n */\nexport const componentsScreenTemplates: ScreenTemplate[] = [\n    ...listTemplates,\n    ...workspaceTemplates,\n    ...commandTemplates,\n    ...editorTemplates,\n    ...nestingChainTemplates,\n];\n\n/**\n * The eight templates that fill the application layout's own `content` slot directly.\n *\n * Kept apart from the nesting chain because `fitsSlot` is resolved against *the containers in scope*, and\n * these two groups are never in scope together. Each of these is a whole page an application places on its\n * own; the chain's three are one page assembled from three levels. Resolving them as one set would ask\n * `resolveScreenTemplates` which of eight `body`-declaring templates the feature section belongs to, and it\n * would rightly answer that it cannot tell.\n */\nexport const componentsPageTemplates: ScreenTemplate[] = [...listTemplates, ...workspaceTemplates, ...commandTemplates, ...editorTemplates];\n"],"names":["componentsScreenTemplates","listTemplates","workspaceTemplates","commandTemplates","editorTemplates","nestingChainTemplates","componentsPageTemplates"],"mappings":";;;;;;AAAA;AACA;AASA;;;;;;UAOaA,yBAAAA,GAA8C;AACpDC,IAAAA,GAAAA,aAAAA;AACAC,IAAAA,GAAAA,kBAAAA;AACAC,IAAAA,GAAAA,gBAAAA;AACAC,IAAAA,GAAAA,eAAAA;AACAC,IAAAA,GAAAA;;AAGP;;;;;;;;UASaC,uBAAAA,GAA4C;AAAIL,IAAAA,GAAAA,aAAAA;AAAkBC,IAAAA,GAAAA,kBAAAA;AAAuBC,IAAAA,GAAAA,gBAAAA;AAAqBC,IAAAA,GAAAA;;;;;"}

package/dist/esm/templates/workspaceTemplates.d.ts

@@ -0,0 +1,5 @@
+import { ScreenTemplate } from '@cratis/scene.model';
+export declare const masterDetailPageTemplate: ScreenTemplate;
+export declare const dashboardPageTemplate: ScreenTemplate;
+export declare const workspaceTemplates: ScreenTemplate[];
+//# sourceMappingURL=workspaceTemplates.d.ts.map

package/dist/esm/templates/workspaceTemplates.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"workspaceTemplates.d.ts","sourceRoot":"","sources":["../../../templates/workspaceTemplates.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,cAAc,EAAkB,MAAM,qBAAqB,CAAC;AA+CrE,eAAO,MAAM,wBAAwB,EAAE,cAkCtC,CAAC;AAYF,eAAO,MAAM,qBAAqB,EAAE,cA+DnC,CAAC;AAGF,eAAO,MAAM,kBAAkB,EAAE,cAAc,EAAsD,CAAC"}