@fusion.dev/helix 0.97.0 → 0.99.0

package/custom-elements.json

@@ -56868,6 +56868,18 @@
             }
           ],
           "members": [
+            {
+              "kind": "field",
+              "name": "icon",
+              "type": {
+                "text": "HelixIcon | undefined"
+              },
+              "description": "The icon itself, for a consumer who imported one.\n\n**The scalable door, and the one this library uses internally.** An icon is\ndata, `{ content, name, viewBox }`, so a value imported by name ships one\nglyph rather than the set, a weight is a subpath rather than an index of\nevery weight, and the supply stops being ours: anything exporting that\nshape works, whether it is Phosphor at another weight, Lucide, or a\nconsumer's own drawings.\n\n**A property and not an attribute**, because an object is not a string. The\nframeworks set properties and plain markup cannot, which is what `name` is\nfor. Set both and this wins, the value being the more specific statement.",
+              "inheritedFrom": {
+                "name": "HelixHeadlessIcon",
+                "module": "src/icon/root/icon-root.ts"
+              }
+            },
             {
               "kind": "field",
               "name": "label",
@@ -56903,7 +56915,7 @@
                 "text": "string"
               },
               "default": "''",
-              "description": "Name of the icon in the Helix set.",
+              "description": "Name of the icon in the Helix set.\n\n**A lookup, and the reason both this and `icon` exist.** A name is a string,\nso it is what markup can carry, and resolving one means an index of the\nwhole set that no bundler can shake: 15 kB for a consumer who renders one\nmark. An attribute is the only thing an HTML author can write, and that is\nworth the index; a consumer who would rather not pay it hands over the\nvalue instead.",
               "attribute": "name",
               "inheritedFrom": {
                 "name": "HelixHeadlessIcon",
@@ -57299,7 +57311,7 @@
                 "text": "string"
               },
               "default": "''",
-              "description": "Name of the icon in the Helix set.",
+              "description": "Name of the icon in the Helix set.\n\n**A lookup, and the reason both this and `icon` exist.** A name is a string,\nso it is what markup can carry, and resolving one means an index of the\nwhole set that no bundler can shake: 15 kB for a consumer who renders one\nmark. An attribute is the only thing an HTML author can write, and that is\nworth the index; a consumer who would rather not pay it hands over the\nvalue instead.",
               "fieldName": "name",
               "inheritedFrom": {
                 "name": "HelixHeadlessIcon",

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.97.0",
+  "version": "0.99.0",
   "license": "MIT",
   "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
   "repository": {
@@ -47,13 +47,13 @@
   },
   "bugs": "https://github.com/project-fusion/fusion/issues",
   "dependencies": {
-    "@fusion.dev/helix-core": "0.97.0",
-    "@fusion.dev/helix-headless": "0.97.0",
-    "@fusion.dev/helix-styles": "0.97.0"
+    "@fusion.dev/helix-core": "0.99.0",
+    "@fusion.dev/helix-headless": "0.99.0",
+    "@fusion.dev/helix-styles": "0.99.0"
   },
   "devDependencies": {
-    "@fusion.dev/helix-cem": "0.97.0",
-    "@fusion.dev/helix-testing": "0.97.0",
+    "@fusion.dev/helix-cem": "0.99.0",
+    "@fusion.dev/helix-testing": "0.99.0",
     "@fusion.dev/scripts": "0.0.0-dev",
     "@happy-dom/global-registrator": "^20.0.0",
     "@lit-labs/ssr": "^4.1.0",

package/types/jsx.d.ts

@@ -9732,8 +9732,28 @@ Asked for rather than inferred from the name. The names are physical, and
 `arrow-left` drawn pointing right on an Arabic page would be the icon
 disagreeing with its own name for every reader who meant the left. */
   mirror?: (HelixIcon["mirror"]) | undefined;
-  /** Name of the icon in the Helix set. */
+  /** Name of the icon in the Helix set.
+
+**A lookup, and the reason both this and `icon` exist.** A name is a string,
+so it is what markup can carry, and resolving one means an index of the
+whole set that no bundler can shake: 15 kB for a consumer who renders one
+mark. An attribute is the only thing an HTML author can write, and that is
+worth the index; a consumer who would rather not pay it hands over the
+value instead. */
   name?: (HelixIcon["name"]) | undefined;
+  /** The icon itself, for a consumer who imported one.
+
+**The scalable door, and the one this library uses internally.** An icon is
+data, `{ content, name, viewBox }`, so a value imported by name ships one
+glyph rather than the set, a weight is a subpath rather than an index of
+every weight, and the supply stops being ours: anything exporting that
+shape works, whether it is Phosphor at another weight, Lucide, or a
+consumer's own drawings.
+
+**A property and not an attribute**, because an object is not a string. The
+frameworks set properties and plain markup cannot, which is what `name` is
+for. Set both and this wins, the value being the more specific statement. */
+  icon?: (HelixIcon["icon"]) | undefined;
 };
 
 export type HelixIconSolidJsProps = {
@@ -9745,8 +9765,28 @@ Asked for rather than inferred from the name. The names are physical, and
 `arrow-left` drawn pointing right on an Arabic page would be the icon
 disagreeing with its own name for every reader who meant the left. */
   "prop:mirror"?: (HelixIcon["mirror"]) | undefined;
-  /** Name of the icon in the Helix set. */
+  /** Name of the icon in the Helix set.
+
+**A lookup, and the reason both this and `icon` exist.** A name is a string,
+so it is what markup can carry, and resolving one means an index of the
+whole set that no bundler can shake: 15 kB for a consumer who renders one
+mark. An attribute is the only thing an HTML author can write, and that is
+worth the index; a consumer who would rather not pay it hands over the
+value instead. */
   "prop:name"?: (HelixIcon["name"]) | undefined;
+  /** The icon itself, for a consumer who imported one.
+
+**The scalable door, and the one this library uses internally.** An icon is
+data, `{ content, name, viewBox }`, so a value imported by name ships one
+glyph rather than the set, a weight is a subpath rather than an index of
+every weight, and the supply stops being ours: anything exporting that
+shape works, whether it is Phosphor at another weight, Lucide, or a
+consumer's own drawings.
+
+**A property and not an attribute**, because an object is not a string. The
+frameworks set properties and plain markup cannot, which is what `name` is
+for. Set both and this wins, the value being the more specific statement. */
+  "prop:icon"?: (HelixIcon["icon"]) | undefined;
 
   /** Set the innerHTML of the element */
   innerHTML?: (string) | undefined;
@@ -29688,6 +29728,25 @@ export type CustomElements = {
    * `arrow-left` drawn pointing right on an Arabic page would be the icon
    * disagreeing with its own name for every reader who meant the left.
    * - `name`: Name of the icon in the Helix set.
+   *
+   * **A lookup, and the reason both this and `icon` exist.** A name is a string,
+   * so it is what markup can carry, and resolving one means an index of the
+   * whole set that no bundler can shake: 15 kB for a consumer who renders one
+   * mark. An attribute is the only thing an HTML author can write, and that is
+   * worth the index; a consumer who would rather not pay it hands over the
+   * value instead.
+   * - `icon`: The icon itself, for a consumer who imported one.
+   *
+   * **The scalable door, and the one this library uses internally.** An icon is
+   * data, `{ content, name, viewBox }`, so a value imported by name ships one
+   * glyph rather than the set, a weight is a subpath rather than an index of
+   * every weight, and the supply stops being ours: anything exporting that
+   * shape works, whether it is Phosphor at another weight, Lucide, or a
+   * consumer's own drawings.
+   *
+   * **A property and not an attribute**, because an object is not a string. The
+   * frameworks set properties and plain markup cannot, which is what `name` is
+   * for. Set both and this wins, the value being the more specific statement. (property only)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -49500,6 +49559,25 @@ export type CustomElementsSolidJs = {
    * `arrow-left` drawn pointing right on an Arabic page would be the icon
    * disagreeing with its own name for every reader who meant the left.
    * - `name`: Name of the icon in the Helix set.
+   *
+   * **A lookup, and the reason both this and `icon` exist.** A name is a string,
+   * so it is what markup can carry, and resolving one means an index of the
+   * whole set that no bundler can shake: 15 kB for a consumer who renders one
+   * mark. An attribute is the only thing an HTML author can write, and that is
+   * worth the index; a consumer who would rather not pay it hands over the
+   * value instead.
+   * - `icon`: The icon itself, for a consumer who imported one.
+   *
+   * **The scalable door, and the one this library uses internally.** An icon is
+   * data, `{ content, name, viewBox }`, so a value imported by name ships one
+   * glyph rather than the set, a weight is a subpath rather than an index of
+   * every weight, and the supply stops being ours: anything exporting that
+   * shape works, whether it is Phosphor at another weight, Lucide, or a
+   * consumer's own drawings.
+   *
+   * **A property and not an attribute**, because an object is not a string. The
+   * frameworks set properties and plain markup cannot, which is what `name` is
+   * for. Set both and this wins, the value being the more specific statement. (property only)
    * - `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

@@ -4981,8 +4981,28 @@ Asked for rather than inferred from the name. The names are physical, and
 `arrow-left` drawn pointing right on an Arabic page would be the icon
 disagreeing with its own name for every reader who meant the left. */
   mirror?: (HelixIcon["mirror"]) | undefined;
-  /** Name of the icon in the Helix set. */
+  /** Name of the icon in the Helix set.
+
+**A lookup, and the reason both this and `icon` exist.** A name is a string,
+so it is what markup can carry, and resolving one means an index of the
+whole set that no bundler can shake: 15 kB for a consumer who renders one
+mark. An attribute is the only thing an HTML author can write, and that is
+worth the index; a consumer who would rather not pay it hands over the
+value instead. */
   name?: (HelixIcon["name"]) | undefined;
+  /** The icon itself, for a consumer who imported one.
+
+**The scalable door, and the one this library uses internally.** An icon is
+data, `{ content, name, viewBox }`, so a value imported by name ships one
+glyph rather than the set, a weight is a subpath rather than an index of
+every weight, and the supply stops being ours: anything exporting that
+shape works, whether it is Phosphor at another weight, Lucide, or a
+consumer's own drawings.
+
+**A property and not an attribute**, because an object is not a string. The
+frameworks set properties and plain markup cannot, which is what `name` is
+for. Set both and this wins, the value being the more specific statement. */
+  icon?: (HelixIcon["icon"]) | undefined;
 };
 
 export type HelixIconVueEvents = {};