@rozie-ui/data-table-solid 0.2.3 → 0.2.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -10,6 +10,8 @@ npm i @rozie-ui/data-table-solid
10
10
 
11
11
  Peer dependencies: `solid-js + @tanstack/table-core + @tanstack/virtual-core + @rozie-ui/popover-solid`. Install them alongside this package.
12
12
 
13
+ Also installed: `@rozie/runtime-solid` — Rozie's small, tree-shaken runtime helper package (controllable state, keyboard navigation, event modifiers, and safe interpolation). It arrives as a regular dependency, so npm pulls it for you. Your bundler keeps only the helpers this component actually uses — typically a few hundred bytes to a few KB, minified and gzipped. [What's in it and what it costs](https://github.com/One-Learning-Community/rozie.js/blob/main/docs/guide/output-and-runtime.md).
14
+
13
15
  ## Usage
14
16
 
15
17
  Columns may be declared as a `:columns` config array **or** as `<Column>` children (or both — an id-keyed last-write-wins union). Per-cell rendering is one parent `#cell` / `#colHeader` renderer on `<DataTable>`, dispatched by `columnId`, so it works the same with either column form.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rozie-ui/data-table-solid",
3
- "version": "0.2.3",
3
+ "version": "0.2.4",
4
4
  "type": "module",
5
5
  "private": false,
6
6
  "license": "MIT",
@@ -46,7 +46,7 @@
46
46
  ],
47
47
  "dependencies": {
48
48
  "@solid-primitives/keyed": "^1.5.3",
49
- "@rozie/runtime-solid": "0.2.2"
49
+ "@rozie/runtime-solid": "0.6.0"
50
50
  },
51
51
  "peerDependencies": {
52
52
  "solid-js": "^1.8",
@@ -24,6 +24,13 @@
24
24
  */
25
25
  .rozie-data-table-wrap,
26
26
  .rozie-data-table {
27
+ /* NOTE (see file-head comment): most of the tokens below are declared but
28
+ never read via a CSS var() inside THIS component's own scoped <style> —
29
+ that is by design. This is the public surface; the "Wire the PUBLIC
30
+ tokens..." block further down assigns each one onto the short internal
31
+ --rdt-* custom property the component actually reads. A future audit
32
+ must not delete these as dead — they are the intended public API. */
33
+
27
34
  /* ── palette (the few values most consumers will set) ───────────────────── */
28
35
  --rozie-data-table-fg: inherit;
29
36
  --rozie-data-table-accent: #0066cc;
@@ -62,6 +69,14 @@
62
69
  /* ── disabled pagination controls ──────────────────────────────────────── */
63
70
  --rozie-data-table-disabled-opacity: 0.4;
64
71
 
72
+ /* ── virtual scroll (row windowing, req-3/D-06) ─────────────────────────── */
73
+ /* Read with NO fallback at its one use site (`max-height: var(--rozie-data-table-max-height);`
74
+ on `.rdt-scroll`) — when unset the property is invalid at computed-value
75
+ time and the rule behaves as if `max-height` were never declared there,
76
+ i.e. `none` (unbounded). Declaring `none` here is the render-neutral
77
+ equivalent of that unset behavior, made explicit and overridable. */
78
+ --rozie-data-table-max-height: none;
79
+
65
80
  /* ─────────────────────────────────────────────────────────────────────────
66
81
  * Wire the PUBLIC tokens onto the INTERNAL `--rdt-*` the component reads. A
67
82
  * bridge only needs to remap the public tokens above; these passthroughs do