@fusion.dev/helix 0.16.4 → 0.16.6

package/custom-elements.json

@@ -4138,16 +4138,30 @@
               "kind": "field",
               "name": "value",
               "type": {
-                "text": "string"
+                "text": "number | string"
               },
               "default": "''",
-              "description": "The count or short text to show.\n\nAbsent shows a dot, zero shows nothing.",
+              "description": "The count or short text to show.\n\nAbsent shows a dot, zero shows nothing.\n\n**A string, and a number is taken anyway.** What this shows is usually a\ncount, so `value={unread}` is the first thing a React consumer writes, and\na property assignment does not go through the attribute converter that\nwould have made it a string. Read raw it went straight into\n`this.value.trim()`, which threw inside `render` and left the mark showing\nwhatever it had last: measured, a badge set to the number 2 stayed an 8px\ndot with no digit in it, and the console carried\n`TypeError: this.value.trim is not a function`. A component whose whole job\nis showing a count must not lose the count for being handed one.",
               "attribute": "value",
               "inheritedFrom": {
                 "name": "HelixHeadlessBadge",
                 "module": "src/badge/root/badge-root.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "given",
+              "type": {
+                "text": "string"
+              },
+              "privacy": "private",
+              "description": "The value as text, whatever it was set to.",
+              "readonly": true,
+              "inheritedFrom": {
+                "name": "HelixHeadlessBadge",
+                "module": "src/badge/root/badge-root.ts"
+              }
+            },
             {
               "kind": "field",
               "name": "blank",
@@ -4387,10 +4401,10 @@
             {
               "name": "value",
               "type": {
-                "text": "string"
+                "text": "number | string"
               },
               "default": "''",
-              "description": "The count or short text to show.\n\nAbsent shows a dot, zero shows nothing.",
+              "description": "The count or short text to show.\n\nAbsent shows a dot, zero shows nothing.\n\n**A string, and a number is taken anyway.** What this shows is usually a\ncount, so `value={unread}` is the first thing a React consumer writes, and\na property assignment does not go through the attribute converter that\nwould have made it a string. Read raw it went straight into\n`this.value.trim()`, which threw inside `render` and left the mark showing\nwhatever it had last: measured, a badge set to the number 2 stayed an 8px\ndot with no digit in it, and the console carried\n`TypeError: this.value.trim is not a function`. A component whose whole job\nis showing a count must not lose the count for being handed one.",
               "fieldName": "value",
               "inheritedFrom": {
                 "name": "HelixHeadlessBadge",
@@ -24637,6 +24651,11 @@
                 "description": "One query across every column, from a search field the page owns.",
                 "slug": "searching"
               },
+              {
+                "description": "A reading of the range and a choice of page size, either side of the pagination the table draws.",
+                "min": 520,
+                "slug": "summary-and-size"
+              },
               {
                 "description": "Pages of five hundred, each drawn a window at a time.",
                 "slug": "windowed-paging"
@@ -30680,10 +30699,6 @@
                 "description": "The same shares over a half circle, with the total in the opening.",
                 "slug": "arc"
               },
-              {
-                "description": "A column the chart does not plot, still read out when a slice is pointed at.",
-                "slug": "columns-not-plotted"
-              },
               {
                 "description": "The three weights a ring can carry, from full strength to a wash.",
                 "slug": "emphasis"
@@ -31569,10 +31584,6 @@
                 "min": 420,
                 "slug": "events"
               },
-              {
-                "description": "A panel beside the page rather than over it, with the page still usable behind it.",
-                "slug": "inline"
-              },
               {
                 "description": "Glass, so the page it covers stays visible under its own scrim.",
                 "slug": "material"

package/dist/data-table/root/data-table-root.css.js

@@ -61,9 +61,17 @@ padding-block-end: var(--helix-space-sm);
 }
 
 [part="footer"] {
+align-items: center;
+display: flex;
+flex-wrap: wrap;
+gap: var(--helix-space-md);
 padding-block-start: var(--helix-space-sm);
 }
 
+[part="pagination"] {
+margin-inline-start: auto;
+}
+
 [part="empty"],
 [part="loading"] {
 color: var(--helix-color-foreground-subtle);

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fusion.dev/helix",
   "description": "Styled component tier. Extends the headless tier with token-driven presentation.",
-  "version": "0.16.4",
+  "version": "0.16.6",
   "license": "MIT",
   "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
   "repository": {
@@ -46,14 +46,14 @@
   },
   "bugs": "https://github.com/project-fusion/fusion/issues",
   "dependencies": {
-    "@fusion.dev/helix-core": "0.16.4",
-    "@fusion.dev/helix-headless": "0.16.4",
-    "@fusion.dev/helix-styles": "0.16.4"
+    "@fusion.dev/helix-core": "0.16.6",
+    "@fusion.dev/helix-headless": "0.16.6",
+    "@fusion.dev/helix-styles": "0.16.6"
   },
   "devDependencies": {
     "@custom-elements-manifest/analyzer": "^0.11.0",
-    "@fusion.dev/helix-cem": "0.16.4",
-    "@fusion.dev/helix-testing": "0.16.4",
+    "@fusion.dev/helix-cem": "0.16.6",
+    "@fusion.dev/helix-testing": "0.16.6",
     "@fusion.dev/scripts": "0.0.0-dev",
     "@happy-dom/global-registrator": "^20.0.0",
     "@lit-labs/ssr": "^3.3.0",

package/types/jsx.d.ts

@@ -1151,7 +1151,17 @@ Past it the indicator reads `{max}+`. */
   max?: (HelixBadge["max"]) | undefined;
   /** The count or short text to show.
 
-Absent shows a dot, zero shows nothing. */
+Absent shows a dot, zero shows nothing.
+
+**A string, and a number is taken anyway.** What this shows is usually a
+count, so `value={unread}` is the first thing a React consumer writes, and
+a property assignment does not go through the attribute converter that
+would have made it a string. Read raw it went straight into
+`this.value.trim()`, which threw inside `render` and left the mark showing
+whatever it had last: measured, a badge set to the number 2 stayed an 8px
+dot with no digit in it, and the console carried
+`TypeError: this.value.trim is not a function`. A component whose whole job
+is showing a count must not lose the count for being handed one. */
   value?: (HelixBadge["value"]) | undefined;
 };
 
@@ -1169,7 +1179,17 @@ Past it the indicator reads `{max}+`. */
   "prop:max"?: (HelixBadge["max"]) | undefined;
   /** The count or short text to show.
 
-Absent shows a dot, zero shows nothing. */
+Absent shows a dot, zero shows nothing.
+
+**A string, and a number is taken anyway.** What this shows is usually a
+count, so `value={unread}` is the first thing a React consumer writes, and
+a property assignment does not go through the attribute converter that
+would have made it a string. Read raw it went straight into
+`this.value.trim()`, which threw inside `render` and left the mark showing
+whatever it had last: measured, a badge set to the number 2 stayed an 8px
+dot with no digit in it, and the console carried
+`TypeError: this.value.trim is not a function`. A component whose whole job
+is showing a count must not lose the count for being handed one. */
   "prop:value"?: (HelixBadge["value"]) | undefined;
 
   /** Set the innerHTML of the element */
@@ -19006,6 +19026,16 @@ export type CustomElements = {
    * - `value`: The count or short text to show.
    *
    * Absent shows a dot, zero shows nothing.
+   *
+   * **A string, and a number is taken anyway.** What this shows is usually a
+   * count, so `value={unread}` is the first thing a React consumer writes, and
+   * a property assignment does not go through the attribute converter that
+   * would have made it a string. Read raw it went straight into
+   * `this.value.trim()`, which threw inside `render` and left the mark showing
+   * whatever it had last: measured, a badge set to the number 2 stayed an 8px
+   * dot with no digit in it, and the console carried
+   * `TypeError: this.value.trim is not a function`. A component whose whole job
+   * is showing a count must not lose the count for being handed one.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -34971,6 +35001,16 @@ export type CustomElementsSolidJs = {
    * - `value`: The count or short text to show.
    *
    * Absent shows a dot, zero shows nothing.
+   *
+   * **A string, and a number is taken anyway.** What this shows is usually a
+   * count, so `value={unread}` is the first thing a React consumer writes, and
+   * a property assignment does not go through the attribute converter that
+   * would have made it a string. Read raw it went straight into
+   * `this.value.trim()`, which threw inside `render` and left the mark showing
+   * whatever it had last: measured, a badge set to the number 2 stayed an 8px
+   * dot with no digit in it, and the console carried
+   * `TypeError: this.value.trim is not a function`. A component whose whole job
+   * is showing a count must not lose the count for being handed one.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by

package/types/vue.d.ts

@@ -608,7 +608,17 @@ Past it the indicator reads `{max}+`. */
   max?: (HelixBadge["max"]) | undefined;
   /** The count or short text to show.
 
-Absent shows a dot, zero shows nothing. */
+Absent shows a dot, zero shows nothing.
+
+**A string, and a number is taken anyway.** What this shows is usually a
+count, so `value={unread}` is the first thing a React consumer writes, and
+a property assignment does not go through the attribute converter that
+would have made it a string. Read raw it went straight into
+`this.value.trim()`, which threw inside `render` and left the mark showing
+whatever it had last: measured, a badge set to the number 2 stayed an 8px
+dot with no digit in it, and the console carried
+`TypeError: this.value.trim is not a function`. A component whose whole job
+is showing a count must not lose the count for being handed one. */
   value?: (HelixBadge["value"]) | undefined;
 };