@supersoniks/concorde 4.7.3 → 4.8.0

package/docs/src/core/components/functional/router/router.md

@@ -1,94 +0,0 @@
-# Router
-
-**sonic-router** watches `document.location` (pathname + hash) and renders the matching view.
-
-From a **Lit** parent, pass a **`.routes`** map (property binding — same rule as [`.items` on list](#core/components/functional/list/list.md/list)): keys are path patterns, values are render functions. Use **`fallback`** when nothing matches.
-
-Legacy HTML **`<template data-route="…">`** remains for hosts without Lit — [HTML integration](#docs/_misc/html-integration.md/html-integration).
-
-## Static routes (no parameters)
-
-Route keys are matched against `pathname + hash`. A simple hash route `#home` matches when the location contains that segment.
-
-On the **doc site**, the page URL is already a hash (`#…/router.md/router`). Demos append a **second** hash for in-page routes (`#…/router#home`), use **`href` + `autoActive="strict"`** on `sonic-button` for the active state, and `history.replaceState` on click so markdown is not reloaded (`setDocsDemoSubHash` in `src/docs/docs-location.ts`).
-
-<docs-lit-demo for="docs-router-basic-demo"></docs-lit-demo>
-
-```typescript
-@state()
-private routes = {
-  "#home": () => html`<div>Home</div>`,
-  "#about": () => html`<div>About</div>`,
-  fallback: () => html`<div>Not found</div>`,
-};
-
-html`
-  <sonic-button href="#home">Home</sonic-button>
-  <sonic-router .routes=${this.routes}></sonic-router>
-`;
-```
-
-| Key | When it runs |
-|-----|----------------|
-| `"#home"`, `"#about"`, … | `RegExp` or [url-pattern](https://www.npmjs.com/package/url-pattern) test succeeds on current location |
-| **`fallback`** | No other route matched (not an attribute — a key on the same object) |
-
-## Routes with parameters
-
-Two styles (see `router.demo.ts` and `docs-router-params-demo`):
-
-### Url-pattern (`:name`)
-
-Key uses **`:param`** segments. The render function receives an **object** `{ param: string }`.
-
-<docs-lit-demo for="docs-router-params-demo"></docs-lit-demo>
-
-```typescript
-"#couleur/:id": ({ id }) => html`<p>Colour id: ${id}</p>`,
-```
-
-### RegExp (capturing groups)
-
-Key is a **RegExp** string with `(\d+)` / `(\w+)` groups. The render function receives an **array** of captured strings (in order).
-
-```typescript
-"#products/(\\d+)/(\\w+)": ([productId, slug]) =>
-  html`<p>Product ${productId}, slug ${slug}</p>`,
-```
-
-With parameters you usually render data directly in Lit (`${id}`). The old **`<template data-route>` + `dataProviderExpression`** pattern scoped a `dataProvider` for `data-bind` / fetch children — prefer **`@subscribe`** or explicit props when using `.routes`.
-
-## `.routes` binding
-
-Always use **`.routes=${…}`** in Lit templates: route handlers are functions and must be set as **properties**, not HTML attributes.
-
-## Optional attributes
-
-| Attribute | Role |
-|-----------|------|
-| **`basePath`** | Prefix for pattern matching (default allows optional leading segments) |
-| **`fallBackRoute`** | If set and no template/route matches, navigates to this URL (redirect). Distinct from **`routes.fallback`** which only renders content |
-
-## `sonic-redirect`
-
-Separate component: redirect when data appears on a publisher (login steps, wizards). Not part of the `.routes` map.
-
-<sonic-code>
-  <template>
-    <sonic-redirect to="#core/components/functional/router/router.md/router#data-is-set" dataProvider="stupid-data-set-id" onData="theData"></sonic-redirect>
-    <div class="flex gap-2 mb-4" formDataProvider="stupid-data-set-id">
-      <sonic-button radio name="theData" value="Some Data" size="xs">
-        Enter data
-      </sonic-button>
-      <sonic-button radio name="theData" value="" href="javascript:history.back();" size="xs">
-        Delete the data and do a history.back()
-      </sonic-button>
-    </div>
-  </template>
-</sonic-code>
-
-Example: combine with **`.routes`** and **submit** for login / logout / profile steps.
-
-## Package demo
-
-`sonic-router-demo` (`router.demo.ts`) — home, user profile (`#user/:id/:slug`), products RegExp, **fallback** 404.

package/docs/src/core/components/functional/sdui/default-library.json

@@ -1,108 +0,0 @@
-{
-    "checkbox": {
-        "tagName": "sonic-checkbox"
-    },
-    "date": {
-        "tagName": "sonic-input",
-        "attributes": {
-            "type": "date"
-        }
-    },
-    "fieldset": {
-        "tagName": "sonic-fieldset",
-        "nodes":[{"libraryKey":"formLayout"}],
-        "contentElementSelector":"sonic-form-layout"
-    },
-    "managed_file": {
-        "tagName": "sonic-input",
-        "attributes": {
-            "variant":"ghost",
-            "type": "file"
-        }
-    },
-    "password": {
-        "tagName": "sonic-input",
-        "attributes": {
-            "type": "password"
-        }
-    },
-    "radio": {
-        "tagName": "sonic-radio"
-    },
-    "select": {
-        "tagName": "sonic-select"
-    },
-    "textarea": {
-        "tagName": "sonic-textarea"
-    },
-    "textfield": {
-        "tagName": "sonic-input",
-        "attributes": {
-            "type": "text"
-        }
-    },
-    "hidden": {
-        "tagName": "sonic-input",
-        "attributes": {
-            "type": "hidden"
-        }
-    },
-    "button": {
-        "tagName": "sonic-button"
-    },
-    "form": {
-        "tagName": "sonic-submit",
-        "attributes": {
-            "onEnterKey": true
-        }
-    },
-    "submit": {
-        "tagName": "sonic-submit",
-        "attributes": {
-            "onClick": true
-        },
-        "contentElementSelector":"sonic-button",
-        "nodes":[
-            {
-                "libraryKey":"button",
-                "attributes":{"type":"success"},
-                "nodes":[
-                    {
-                        "tagName":"sonic-icon",
-                        "attributes":{
-                            "name":"check",
-                            "slot":"prefix"
-                        }
-                    }
-                ]
-            }
-        ]
-    },
-    "email": {
-        "tagName": "sonic-input",
-        "attributes": {
-            "type": "email"
-        }
-    },
-    "formItemContainer": {
-        "tagName": "div",
-        "attributes": {
-            "class": "form-item-container"
-        }
-    },
-    "formLayout": {
-        "tagName": "sonic-form-layout"
-    },
-    "formActions": {
-        "tagName": "sonic-form-actions"
-    },
-    "passwordHelper": {
-        "tagName": "sonic-password-helper"
-    },
-    "sameValueHelper": {
-        "tagName": "sonic-same-value-helper"
-    },
-    "divider": {
-        "tagName": "sonic-divider"
-    }
-}

package/docs/src/core/components/functional/sdui/example.json

@@ -1,99 +0,0 @@
-{
-  "nodes": [
-    {
-      "tagName": "div",
-      "attributes": {
-        "class": "flex gap-2 items-center",
-        "formdataprovider": "states-basic-example"
-      },
-      "nodes": [
-        {
-          "tagName": "sonic-button",
-          "attributes": {
-            "radio": "",
-            "name": "selection",
-            "value": "#home",
-            "checked": "",
-            "size": "xs"
-          },
-          "innerHTML": "Home"
-        },
-        {
-          "tagName": "sonic-button",
-          "attributes": {
-            "radio": "",
-            "name": "selection",
-            "value": "#about",
-            "size": "xs"
-          },
-          "innerHTML": "About"
-        },
-        {
-          "tagName": "sonic-button",
-          "attributes": {
-            "radio": "",
-            "name": "selection",
-            "value": "#work",
-            "size": "xs"
-          },
-          "innerHTML": "Work"
-        },
-        {
-          "tagName": "sonic-button",
-          "attributes": {
-            "radio": "",
-            "name": "selection",
-            "value": "#contact",
-            "size": "xs"
-          },
-          "innerHTML": "Contact"
-        }
-      ]
-    },
-    {
-      "tagName": "div",
-      "attributes": {
-        "class": "text-center text-neutral-700 border rounded text-4xl  my-6 p-3 "
-      },
-      "nodes": [
-        {
-          "tagName": "sonic-states",
-          "attributes": {
-            "dataprovider": "states-basic-example",
-            "data-path": "selection"
-          },
-          "nodes": [
-            {
-              "tagName": "template",
-              "attributes": {
-                "data-value": "#home"
-              },
-              "innerHTML": "Home"
-            },
-            {
-              "tagName": "template",
-              "attributes": {
-                "data-value": "#about"
-              },
-              "innerHTML": "About"
-            },
-            {
-              "tagName": "template",
-              "attributes": {
-                "data-value": "#work"
-              },
-              "innerHTML": "Work"
-            },
-            {
-              "tagName": "template",
-              "attributes": {
-                "data-value": "#contact"
-              },
-              "innerHTML": "Contact"
-            }
-          ]
-        }
-      ]
-    }
-  ]
-}

package/docs/src/core/components/functional/sdui/sdui.md

@@ -1,356 +0,0 @@
-# SDUI
-
-## What is SDUI?
-
-SDUI stands for `Server Driven User Interfaces`.
-Basically, it generates a user interface based on a JSON SDUI Descriptor.
-
-### Subscriber extension:
-
-SDUI extends the mixin [Subscriber](#docs/_core-concept/subscriber.md/subscriber).
-This means that you must set a dataProvider with an id pointing to the publisher that will hold your SDUI Descriptor.
-This also means that it has a reactive property named `props` that you can set with the JSON SDUI Descriptor in order to configure it.
-
-### Fetcher extension:
-
-SDUI extends the mixin Fetcher as [Fetch](#core/components/functional/fetch/fetch.md/fetch) and [List](#core/components/functional/list/list.md/list).
-
-In this case, it will parse the JSON coming from the request.
-The JSON must comply with the SDUI descriptor format.
-
-As a fetcher, invalidating the publisher or updating the endpoint will trigger a new fetch and update accordingly.
-
-### Rendering:
-
-It has no shadowdom, and its display style is set to `contents`, so an empty SDUI has the fewest impact on the layout.
-
-## SDUI descriptor
-
-### TypeScript definition:
-<sonic-code language="typescript">
-  <template>
-    export type SDUIDescriptor = {
-      js?: Array&lt;string&gt;;
-      css?: Array&lt;string&gt;;
-      library?: Record&lt;string, SDUINode&gt;;
-      nodes?: Array&lt;SDUINode&gt;;
-    };
-  </template>
-</sonic-code>
-
-### Meaning of the keys:
-
-* **js**: An array of URLs pointing to JavaScript files to load.
-* **css**: An array of URLs pointing to CSS files to load.
-* **library**: A record of SDUINode definitions intended to be used as a model for other nodes. The keys of the record can be used as the libraryKey of the node. This node will then specialize the model with its own descriptor.
-* **nodes**: An array of SDUINode descriptors. Each SDUINode will result in an HTMLElement added to the root of the component.
-
-## SDUINode
-
-### Descriptor
-
-An SDUINode represents an HTMLElement.
-
-TypeScript definition:
-
-<sonic-code language="typescript">
-  <template>
-    export type SDUINode = {
-      markup?: string;
-      tagName?: string;
-      attributes?: Record&lt;string, string&gt;;
-      nodes?: Array&lt;SDUINode&gt;;
-      innerHTML?: string;
-      prefix?: string;
-      suffix?: string;
-      libraryKey?: string;
-      contentElementSelector?: string;
-      parentElementSelector?: string;
-    };
-  </template>
-</sonic-code>
-
-Summary of properties:
-* **markup**: Use it if you prefer to define your node entirely using an HTML string.
-* **tagName**: The tag name of the HTML element.
-* **attributes**: A string key/value pair storing each attribute name/value of the HTML element created.
-* **nodes**: An array of SDUINode descriptors. The children of the HTMLElement are created this way.
-* **innerHTML**: The inner HTML of the current node is defined here if needed.
-* **prefix**: Use it if you want to wrap the component with some HTML string in conjunction with the suffix.
-* **suffix**: Use it if you want to wrap the component with some HTML string in conjunction with the prefix.
-* **libraryKey**: An identifier that points to an SDUINode to be used as a model for this node.
-* **contentElementSelector**: For SDUINodes defined in the library only. It is a CSS selector that defines where child nodes are added.
-* **parentElementSelector**: If the current node, as a future child, has a `parentElementSelector` attribute, it is added to the node corresponding to the associated CSS selector rather than directly to the element.
-
-### Markup
-Use it if you prefer to define your node entirely using an HTML string.
-
-<sonic-code>
-  <template>
-    <sonic-sdui 
-      dataProvider="sdui-markup-example" 
-      props='{
-          "nodes":[
-            {
-              "markup":"keep shouting <sonic-badge>foo</sonic-badge> <sonic-badge>bar</sonic-badge> !"
-            }
-          ]}'
-    ></sonic-sdui>
-  </template>
-</sonic-code>
-
-### Tag name
-Here we use the field `tagName` of SDUINode to create an element with tag name `sonic-input`.
-
-<sonic-code>
-  <template>
-    <sonic-sdui 
-      dataProvider="sdui-tagName-example" 
-      props='{
-          "nodes":[
-            {
-              "tagName":"sonic-input"
-            }
-          ]}'
-    ></sonic-sdui>
-  </template>
-</sonic-code>
-
-### Attributes
-A string key/value pair storing each attribute name/value of the HTML element created.
-As no tag name is defined, a div element is created.
-Here we define the style attribute to create a tiny red square.
-
-<sonic-code>
-  <template>
-    <sonic-sdui 
-      dataProvider="sdui-attributes-example" 
-      props='{
-        "nodes":[{
-          "attributes":{
-            "style":"width:50px;height:10px;background:red;"
-          }
-        }]
-      }'
-    ></sonic-sdui>
-  </template>
-</sonic-code>
-
-### Nodes
-Children of the current node can be added using the field `nodes` recursively.
-
-<sonic-code>
-  <template>
-    <sonic-sdui 
-      dataProvider="sdui-nodes-example" 
-      props='{
-        "nodes":[{
-          "nodes":[
-            {"innerHTML":"A"},
-            {
-              "prefix":"B",
-              "nodes":[
-                {"innerHTML":"👉 B.1"},
-                {"innerHTML":"👉 B.2"}
-              ]
-            }
-          ]
-        }]
-      }'
-    ></sonic-sdui>
-  </template>
-</sonic-code>
-
-### InnerHTML
-As no tag name is defined, a div element is created, and then we use `innerHTML` to add content to it.
-
-<sonic-code>
-  <template>
-    <sonic-sdui 
-      dataProvider="sdui-html-example" 
-      props='{
-        "nodes":[{
-          "innerHTML":"keep shouting <sonic-badge>foo</sonic-badge> <sonic-badge>bar</sonic-badge> !"
-        }]
-      }'
-    ></sonic-sdui>
-  </template>
-</sonic-code>
-
-### Prefix and suffix
-Use them if you want to wrap the component with some HTML string.
-
-<sonic-code>
-  <template>
-    <sonic-sdui 
-      dataProvider="sdui-prefixSuffix-example" 
-      props='{
-        "nodes":[{
-          "prefix":"👇",
-          "suffix":"☝️",
-          "innerHTML":"The node content"
-        }]
-      }'
-    ></sonic-sdui>
-  </template>
-</sonic-code>
-
-### Library key and contentElementSelector
-The libraryKey of SDUINode is an identifier that points to an SDUINode description in the library to be used as a model for this node.
-
-Note that the SDUI has a default library containing some basic component definitions useful for form declaration (see default-library.json).
-
-This example uses the library key `submit` which points to a `sonic-submit` containing a button also coming from the library.
-
-The element named `button` in the library is a `sonic-button` of type `success` containing a check icon as a prefix.
-
-Since the `submit` library element contains an attribute `contentElementSelector` with the value `sonic-button`, the "injected content" is put inside the button.
-
-We used `innerHTML` for the sake of simplicity, but you can use nodes to add any complex content.
-
-<sonic-code>
-  <template>
-    <sonic-sdui dataProvider="sdui-library-example" props='
-          {
-            "nodes":[
-              {
-                "libraryKey":"submit",
-                "innerHTML":"Injected content"
-              }
-            ]
-          }
-    '></sonic-sdui>
-  </template>
-</sonic-code>
-
-### parentElementSelector
-
-This special field lets you inject the content at any place in the HTML flow already set inside the parent SDUI component by using a CSS selector.
-
-⚠️ Note that it doesn't work with top-level nodes.
-
-<sonic-code>
-  <template>
-    <sonic-sdui dataProvider="sdui-parentElementSelector-example" props='
-          {
-            "nodes":[
-              {
-                "nodes":[
-                  {
-                    "prefix":"👇 Selected parent element",
-                    "suffix":"☝️ End of selected parent element",
-                    "tagName":"span"
-                  },
-                  {
-                    "parentElementSelector":"span",
-                    "innerHTML":"Content having a parentElementSelector attribute"
-                  }
-                ]
-              }
-            ]
-          }
-    '></sonic-sdui>
-  </template>
-</sonic-code>
-
-### Fetch example:
-
-<sonic-code>
-  <template>
-    <sonic-sdui dataProvider="sdui-fetch-example" endPoint="/src/core/components/functional/sdui/example.json"></sonic-sdui>
-  </template>
-</sonic-code>
-
-## Transformers:
-
-The transformers let you transform the structure of the SDUI Descriptor into a new one before parsing and rendering it.
-
-To enable it, you must fill the `transformation` attribute of the component with a URL pointing to a Transform descriptor.
-
-<sonic-code language="typescript">
-  <template>
-  export type SDUITransformDescription = {
-    library?: Record&lt;string, SDUINode&gt;;
-    transforms: Array&lt;SDUITransformAction&gt;;
-  };
-  </template>
-</sonic-code>
-
-### The library:
-
-Each key of the library will be merged with the current library in the SDUI Descriptor, by replacing or creating items library key by key.
-
-### The transform actions:
-
-Each transform represents an action that will be done on the SDUI descriptor before the creation of the entire UI.
-
-<sonic-code language="typescript">
-  <template>
-export type SDUITransformAction = {
-  action: SDUITransformActionName;
-  patterns?: Array&lt;SDUINode&gt;;
-  after?: SDUINode;
-  before?: SDUINode;
-  in?: SDUINode;
-  ui?: SDUINode;
-};
-  </template>
-</sonic-code>
-
-The action that will be done is a verb:
-
-<sonic-code language="typescript">
-  <template>
-export type SDUITransformActionName = "remap" | "unwrap" | "wrap" | "delete" | "insert" | "move";
-  </template>
-</sonic-code>
-
-* **remap**: The properties (tagName, innerHTML, etc.) of the targeted SDUINode will be created/changed according to their presence in the `ui` (SDUINode) property of the transformAction.
-* **unwrap**: Replaces the targeted SDUINode in place with its children.
-* **wrap**: Groups all SDUINodes targeted by the patterns into the new SDUINode described in the `ui` prop of the transformAction.
-* **delete**: Deletes the targeted item.
-* **insert**: Inserts a new SDUINode described by the `ui` prop into the flow. The position of insertion depends on the presence of the attributes `before`, `after`, `in`, which is a pattern to target an existing SDUINode.
-
-## Misc Tricks:
-
-### sduiKey
-
-This is an HTML attribute to set on the component if needed. In this case, the component will not treat its props value directly as an SDUI descriptor. Internally, it will basically extract the SDUIDescriptor by doing something like this: `const sduiDescriptor = this.props[this.sduikey]`.
-
-### messageKey
-
-This is an HTML attribute to set on the component if needed. In this case, the component will automatically create a `sonic-toast-message-subscriber` component. The data found in `props[messageKey]` will be treated as the data expected by the `sonic-toast-message-subscriber`. So, by respecting the format of data supported by this component, you will be able to show multiple toasts in the result of a request.
-
-Example of JSON with `messageKey`=`messages`:
-<sonic-code language="typescript">
-  <template>
-{
-  "messages": [{
-    "content": "The product has been added to your cart", 
-    "status": "success", 
-    "type": "public"
-  }]
-}
-  </template>
-</sonic-code>
-
-### library
-
-This is an HTML attribute to set on the component if needed. You can set a URL pointing to a JSON describing a library with the same structure as the library in the SDUIDescriptor. The component will simply override its library with the given one.
-
-## Playground
-
-Here is a little playground to let you test some simple tricks.
-
-<sonic-code>
-  <template>
-    <sonic-textarea 
-    rows="10" 
-    onChange="SonicPublisherManager.get('sdui-playground').set(JSON.parse(this.value))" 
-    value='{"nodes":[{"tagName":"div", "innerHTML":"test"}]}'
-    >
-    </sonic-textarea>
-    <sonic-sdui dataProvider="sdui-playground" props='{"nodes":[{"tagName":"div", "innerHTML":"test"}]}'>
-    </sonic-sdui>
-  </template>
-</sonic-code>