@livenetworks/ashlar 2.1.13 → 2.2.0

package/components/COMPONENTS.md

@@ -211,86 +211,86 @@ function _domObserver() {
 
 ---
 
-## Reactive Rendering Pattern
-
-When a component has **multiple internal state properties** or frequent updates that drive DOM updates, use `createBatcher` + `fill()` from ln-core. This eliminates manual querySelector chains and coalesces multiple synchronous state changes into a single DOM update.
-
-### The core primitives
-
-| Helper | Role |
-|--------|------|
-| `createBatcher(renderFn, afterRender)` | Coalesces sync state changes into one `renderFn` call via `queueMicrotask` |
-| `fill(root, data)` | Writes state to DOM via `data-ln-field`, `data-ln-attr`, `data-ln-show`, `data-ln-class` |
-
-### Pattern
-
-```javascript
-import { createBatcher, fill, dispatch } from '../ln-core';
-
-function _component(dom) {
-    this.dom = dom;
-    const self = this;
-
-    this.state = { key: null, value: null };
-
-    this.queueRender = createBatcher(
-        function () {
-            if (!self._destroyed) {
-                self._render();
-            }
-        },      // runs after current sync block
-        function () {
-            if (!self._destroyed) {
-                self._afterRender();
-            }
-        }  // runs after render — dispatch events here
-    );
-}
-
-_component.prototype._render = function () {
-    fill(this.dom, this.state);
-    // additional DOM logic derived from state
-};
-
-_component.prototype._afterRender = function () {
-    dispatch(this.dom, 'ln-component:changed', { key: this.state.key });
-};
-
-_component.prototype.update = function (key, value) {
-    this.state.key = key;
-    this.state.value = value;
-    this.queueRender(); // Multiple sync updates trigger exactly ONE render pass
-};
-```
-
-When multiple properties change in the same sync block:
-
-```javascript
-this.state.key = 'status';
-this.state.value = 'active';
-this.queueRender();
-// → microtask fires → _render() once → _afterRender() once
-```
-
-### `fill()` — limitations
-
-`fill()` sets `textContent` for `data-ln-field` — it does **not** set `.value` on `<input>`, `<textarea>`, or `<select>`. For form elements, set `.value` manually after `fill()`.
-
-### When to use
-
-Use `createBatcher` when a component has **frequent or multiple state updates** (e.g. search input, filter checkboxes, sorting), and multiple updates can occur in the same synchronous cycle.
-
-**Don't use it for:**
-- Single boolean state — `this.isOpen = true; dom.classList.toggle(...)` is simpler
-- Event-driven rendering — components that receive data via `set-data` events (ln-table)
-- One-shot renders — clone template + fill once, no ongoing state
-
-### Used in
-
-Used in `ln-search`, `ln-filter`, `ln-list`, and `ln-data-coordinator` for microtask render coalescing.
-
----
-
+## Reactive Rendering Pattern
+
+When a component has **multiple internal state properties** or frequent updates that drive DOM updates, use `createBatcher` + `fill()` from ln-core. This eliminates manual querySelector chains and coalesces multiple synchronous state changes into a single DOM update.
+
+### The core primitives
+
+| Helper | Role |
+|--------|------|
+| `createBatcher(renderFn, afterRender)` | Coalesces sync state changes into one `renderFn` call via `queueMicrotask` |
+| `fill(root, data)` | Writes state to DOM via `data-ln-field`, `data-ln-attr`, `data-ln-show`, `data-ln-class` |
+
+### Pattern
+
+```javascript
+import { createBatcher, fill, dispatch } from '../ln-core';
+
+function _component(dom) {
+    this.dom = dom;
+    const self = this;
+
+    this.state = { key: null, value: null };
+
+    this.queueRender = createBatcher(
+        function () {
+            if (!self._destroyed) {
+                self._render();
+            }
+        },      // runs after current sync block
+        function () {
+            if (!self._destroyed) {
+                self._afterRender();
+            }
+        }  // runs after render — dispatch events here
+    );
+}
+
+_component.prototype._render = function () {
+    fill(this.dom, this.state);
+    // additional DOM logic derived from state
+};
+
+_component.prototype._afterRender = function () {
+    dispatch(this.dom, 'ln-component:changed', { key: this.state.key });
+};
+
+_component.prototype.update = function (key, value) {
+    this.state.key = key;
+    this.state.value = value;
+    this.queueRender(); // Multiple sync updates trigger exactly ONE render pass
+};
+```
+
+When multiple properties change in the same sync block:
+
+```javascript
+this.state.key = 'status';
+this.state.value = 'active';
+this.queueRender();
+// → microtask fires → _render() once → _afterRender() once
+```
+
+### `fill()` — limitations
+
+`fill()` sets `textContent` for `data-ln-field` — it does **not** set `.value` on `<input>`, `<textarea>`, or `<select>`. For form elements, set `.value` manually after `fill()`.
+
+### When to use
+
+Use `createBatcher` when a component has **frequent or multiple state updates** (e.g. search input, filter checkboxes, sorting), and multiple updates can occur in the same synchronous cycle.
+
+**Don't use it for:**
+- Single boolean state — `this.isOpen = true; dom.classList.toggle(...)` is simpler
+- Event-driven rendering — components that receive data via `set-data` events (ln-table)
+- One-shot renders — clone template + fill once, no ongoing state
+
+### Used in
+
+Used in `ln-search`, `ln-filter`, `ln-list`, and `ln-data-coordinator` for microtask render coalescing.
+
+---
+
 ## CustomEvent Communication
 
 Components do NOT know about each other. Communication ONLY via CustomEvent.

package/components/ln-api-connector/ln-api-connector.schema.json

@@ -1,105 +1,105 @@
-{
-	"$comment": "This file is partly generated. The $comment, component, generator, and each attribute's direction, sources, type, values, fallback, and description keys are owned by the generator and synchronized from JS source code. All other keys are preserved and safe to hand-author. Regenerate with `npm run sync:ln-schemas`.",
-	"component": "ln-api-connector",
-	"generator": "scripts/sync-ln-schemas.mjs",
-	"attributes": {
-		"data-ln-api-base-url": {
-			"direction": null,
-			"sources": [
-				"src/ln-api-connector.js"
-			],
-			"type": "string",
-			"fallback": "",
-			"description": "Base URL endpoint for API requests"
-		},
-		"data-ln-api-connector": {
-			"direction": null,
-			"sources": [
-				"src/ln-api-connector.js"
-			],
-			"type": "marker",
-			"description": "Mounts API connector bridging REST backend and ln-ashlar data coordinators"
-		},
-		"data-ln-api-connector-query-debounce": {
-			"direction": "author",
-			"sources": [
-				"src/ln-api-connector.js"
-			],
-			"type": "integer",
-			"fallback": 200,
-			"min": 0,
-			"description": "Debounce delay in milliseconds before dispatching query requests"
-		},
-		"data-ln-api-endpoint": {
-			"direction": "author",
-			"sources": [
-				"src/ln-api-connector.js"
-			],
-			"type": "string",
-			"fallback": "",
-			"description": "Alias for data-ln-api-path"
-		},
-		"data-ln-api-headers": {
-			"direction": null,
-			"sources": [
-				"src/ln-api-connector.js"
-			],
-			"type": "json",
-			"description": "Custom HTTP headers in JSON format or semicolon-separated pairs"
-		},
-		"data-ln-api-param-limit": {
-			"direction": "author",
-			"sources": [
-				"src/ln-api-connector.js"
-			],
-			"type": "string",
-			"fallback": "limit",
-			"description": "Query parameter name for pagination page size"
-		},
-		"data-ln-api-param-offset": {
-			"direction": "author",
-			"sources": [
-				"src/ln-api-connector.js"
-			],
-			"type": "string",
-			"fallback": "offset",
-			"description": "Query parameter name for pagination offset"
-		},
-		"data-ln-api-param-search": {
-			"direction": "author",
-			"sources": [
-				"src/ln-api-connector.js"
-			],
-			"type": "string",
-			"fallback": "search",
-			"description": "Query parameter name for text search filter"
-		},
-		"data-ln-api-param-sort-dir": {
-			"direction": "author",
-			"sources": [
-				"src/ln-api-connector.js"
-			],
-			"type": "string",
-			"fallback": "sort_dir",
-			"description": "Query parameter name for sort direction"
-		},
-		"data-ln-api-param-sort-field": {
-			"direction": "author",
-			"sources": [
-				"src/ln-api-connector.js"
-			],
-			"type": "string",
-			"fallback": "sort_by",
-			"description": "Query parameter name for sort field"
-		},
-		"data-ln-api-path": {
-			"direction": "author",
-			"sources": [
-				"src/ln-api-connector.js"
-			],
-			"type": "string",
-			"fallback": "",
-			"description": "Resource path appended to base URL"
-		}
-	}
-}
+{
+	"$comment": "This file is partly generated. The $comment, component, generator, and each attribute's direction, sources, type, values, fallback, and description keys are owned by the generator and synchronized from JS source code. All other keys are preserved and safe to hand-author. Regenerate with `npm run sync:ln-schemas`.",
+	"component": "ln-api-connector",
+	"generator": "scripts/sync-ln-schemas.mjs",
+	"attributes": {
+		"data-ln-api-base-url": {
+			"direction": null,
+			"sources": [
+				"src/ln-api-connector.js"
+			],
+			"type": "string",
+			"fallback": "",
+			"description": "Base URL endpoint for API requests"
+		},
+		"data-ln-api-connector": {
+			"direction": null,
+			"sources": [
+				"src/ln-api-connector.js"
+			],
+			"type": "marker",
+			"description": "Mounts API connector bridging REST backend and ln-ashlar data coordinators"
+		},
+		"data-ln-api-connector-query-debounce": {
+			"direction": "author",
+			"sources": [
+				"src/ln-api-connector.js"
+			],
+			"type": "integer",
+			"fallback": 200,
+			"min": 0,
+			"description": "Debounce delay in milliseconds before dispatching query requests"
+		},
+		"data-ln-api-endpoint": {
+			"direction": "author",
+			"sources": [
+				"src/ln-api-connector.js"
+			],
+			"type": "string",
+			"fallback": "",
+			"description": "Alias for data-ln-api-path"
+		},
+		"data-ln-api-headers": {
+			"direction": null,
+			"sources": [
+				"src/ln-api-connector.js"
+			],
+			"type": "json",
+			"description": "Custom HTTP headers in JSON format or semicolon-separated pairs"
+		},
+		"data-ln-api-param-limit": {
+			"direction": "author",
+			"sources": [
+				"src/ln-api-connector.js"
+			],
+			"type": "string",
+			"fallback": "limit",
+			"description": "Query parameter name for pagination page size"
+		},
+		"data-ln-api-param-offset": {
+			"direction": "author",
+			"sources": [
+				"src/ln-api-connector.js"
+			],
+			"type": "string",
+			"fallback": "offset",
+			"description": "Query parameter name for pagination offset"
+		},
+		"data-ln-api-param-search": {
+			"direction": "author",
+			"sources": [
+				"src/ln-api-connector.js"
+			],
+			"type": "string",
+			"fallback": "search",
+			"description": "Query parameter name for text search filter"
+		},
+		"data-ln-api-param-sort-dir": {
+			"direction": "author",
+			"sources": [
+				"src/ln-api-connector.js"
+			],
+			"type": "string",
+			"fallback": "sort_dir",
+			"description": "Query parameter name for sort direction"
+		},
+		"data-ln-api-param-sort-field": {
+			"direction": "author",
+			"sources": [
+				"src/ln-api-connector.js"
+			],
+			"type": "string",
+			"fallback": "sort_by",
+			"description": "Query parameter name for sort field"
+		},
+		"data-ln-api-path": {
+			"direction": "author",
+			"sources": [
+				"src/ln-api-connector.js"
+			],
+			"type": "string",
+			"fallback": "",
+			"description": "Resource path appended to base URL"
+		}
+	}
+}

package/components/ln-chart/ln-chart-dev.scss

@@ -1,10 +1,6 @@
 @use '../../theme/config/mixins' as *;
 
 [data-ln-debug] {
-	[data-ln-chart]:not(.chart) {
-		@include dev-dom-error("[data-ln-chart] is missing the required .chart visual class.");
-	}
-
 	[data-ln-chart]:not([data-ln-chart-x]),
 	[data-ln-chart]:not([data-ln-chart-y]) {
 		@include dev-dom-error("[data-ln-chart] requires data-ln-chart-x and data-ln-chart-y.");

package/components/ln-core/README.md

@@ -559,24 +559,24 @@ const batchRender = createBatcher(
 
 ---
 
-## Reactive Rendering Pattern
-
-The `createBatcher` primitive and DOM rendering helpers (`fill`, `renderList`) are designed to be used together as the canonical ln-ashlar microtask render loop:
-
-1. **State mutation.** Component updates internal data properties (e.g. `this.state.key = 'val'`).
-2. **Microtask queue.** The component triggers the `schedule()` function returned by `createBatcher`. Any number of synchronous assignments in the same sync block schedule a single microtask.
-3. **One render.** When the microtask fires, the batcher calls `renderFn` exactly once. `renderFn` typically calls `fill(this.dom, this.state)` (or `renderList` for keyed collections) to project state into the DOM, then the optional `afterRender` callback fires (commonly used to dispatch a `ln-{component}:rendered` or changed event).
-
-Two state assignments on the same tick produce one DOM update:
-
-The pattern is: **state mutation → microtask queue → one render**.
-Never wire sync state updates directly to immediate DOM writes when multiple attributes or filter parameters can change simultaneously — batching prevents layout thrashing.
-
-For further details, see
-[Reactive Rendering Pattern in components/COMPONENTS.md](../../components/COMPONENTS.md#reactive-rendering-pattern).
-
----
-
+## Reactive Rendering Pattern
+
+The `createBatcher` primitive and DOM rendering helpers (`fill`, `renderList`) are designed to be used together as the canonical ln-ashlar microtask render loop:
+
+1. **State mutation.** Component updates internal data properties (e.g. `this.state.key = 'val'`).
+2. **Microtask queue.** The component triggers the `schedule()` function returned by `createBatcher`. Any number of synchronous assignments in the same sync block schedule a single microtask.
+3. **One render.** When the microtask fires, the batcher calls `renderFn` exactly once. `renderFn` typically calls `fill(this.dom, this.state)` (or `renderList` for keyed collections) to project state into the DOM, then the optional `afterRender` callback fires (commonly used to dispatch a `ln-{component}:rendered` or changed event).
+
+Two state assignments on the same tick produce one DOM update:
+
+The pattern is: **state mutation → microtask queue → one render**.
+Never wire sync state updates directly to immediate DOM writes when multiple attributes or filter parameters can change simultaneously — batching prevents layout thrashing.
+
+For further details, see
+[Reactive Rendering Pattern in components/COMPONENTS.md](../../components/COMPONENTS.md#reactive-rendering-pattern).
+
+---
+
 ## window-cache.js
 
 ### createWindowCache(config)
@@ -951,9 +951,9 @@ import { dispatch, dispatchCancelable, guardBody, findElements, createBatcher, f
         const self = this;
 
         // Reactive state + batched rendering
-                this.state = { items: [] };
-        this.batchRender = createBatcher(function () {
-            if (!self._destroyed) self._render();
+                this.state = { items: [] };
+        this.batchRender = createBatcher(function () {
+            if (!self._destroyed) self._render();
         });
 
         return this;